Skip to main content
Approvals let a reviewer sign off on a component’s lineage version — the result of a single analysis run — establishing it as the trusted baseline for that component. Approving a version makes it eligible for export, and Gable tracks any changes made afterward so reviewers can see at a glance whether the current lineage still matches what was signed off.

Approve a version

Approvals are managed from the header of the Component Details page, for the version currently selected in the version selector.
  1. Open Component Details for the component and select the version you want to review.
  2. Select Review changes to step through what changed in this version. Once you’ve reviewed, the control advances to the approve step.
  3. Select Approve version.
  4. In the Approve lineage version for publish dialog, optionally add an approval note summarizing what you reviewed and why you’re approving, then confirm.

The review and approve control on the Component Details header

The approve dialog

Approving records who approved the version, when, and any note, and marks the version as eligible for export.

Approval states

A version’s approval state is shown on the Component Details header, in the version selector, and on the Lineage quality tab:
  • Approved — the version has been reviewed and approved. It is eligible for export.
  • Changes since approval — the version was approved, but the lineage has changed since (for example, a new override). The version may need to be re-approved.
  • Unapproved — the version has not been approved.
The version selector shows an approval badge next to each version, so you can tell at a glance which versions are approved.

Approval badges in the version selector

Re-approving after changes

Because an approval applies to a specific version, edits made after approval — such as adding an override — create pending changes that must be reviewed again. When a version shows Changes since approval, use Re-approve version to review the new changes and sign off again.
Approving establishes the baseline that exported lineage is drawn from. To understand exactly what changed between two versions before approving, see Reviewing Version Changes.