Skip to main content
When a project uses the Pending changes + Save change workflow, saving a draft to main runs through Review & Delivery. This is where you see what changed, assign reviewers, and satisfy any approval rules the project requires before the change can land — the controls that let a regulated team prove every change was checked before it went live.

​
Prerequisites

  • The project’s change workflow is set to Pending changes + Save (or the Git PR variant).
  • You are working on a draft with at least one pending change.

​
The Review & Delivery panel

While you are on a draft, the Review & Delivery panel appears at the bottom of the editor. The Review & Delivery panel showing What's changed, a Reviewers section with Assign reviewer, a Checks section, and Review, Save, and Discard actions Saving prompts you to confirm — it applies your pending changes as the new version for everyone.

​
Approval rules

Approval rules gate a draft’s readiness to reach main. You set them per project, in the same Change Workflow settings where you choose the workflow, under Review rules. The Review rules list with Four-eyes approval enabled, showing its Enforce toggle, minimum approvals, exclude-author, and require-assigned-reviewers options Each rule can be set to Enforce or left as advisory:
  • Enforce — the rule hard-gates apply-to-main. The draft cannot be saved until the rule passes.
  • Advisory — the rule only warns. It surfaces a problem but does not block saving.

​
Available rules

Enable a rule to configure it. For example, Four-eyes approval lets you set:
  • Minimum approvals — how many approvals are needed
  • Exclude author — approvers must differ from the stream author, so no one can approve their own work
  • Require assigned reviewers — every assigned reviewer must approve before the rule passes

​
Save a reviewed draft

  1. On the draft, open the Review & Delivery panel.
  2. Check What’s changed and, if needed, click Review to inspect the diff.
  3. Assign reviewers under Reviewers if the project requires approval.
  4. Make sure every enforced rule under Checks passes.
  5. Click Save and confirm.
Leapter merges the draft into main and records an Apply <draft> entry on the Timeline.
With Four-eyes approval enforced and Exclude author on, you cannot approve your own draft — a second team member has to. Make sure your project has more than one member before enforcing it, or you will not be able to save.

​
What to do next

  • Change Workflow — the setting that turns on drafts and this review flow
  • Timeline — see applied drafts and every version in the change graph
  • Collaborating — leave and resolve review comments on Blueprints