Skip to main content
A new version that needs sign-off gets a review. Waiting on me has the ones that need yours (the sidebar counts them), My submissions has versions you pushed, Everything pending has every open review for people who manage governance, and History has every decision, including releases by override. Automation changes lists flow changes waiting for review.

A review

A review shows the version’s summary, its level and why it needs review, its tags, where it runs, and each required sign-off with who can give it. Its status is Pending, Released, Released by override, Changes requested, Kept blocked or Withdrawn. You can Sign off, Request changes with a note, or correct the version’s tags with a reason for each change, saved with your decision. Once every required sign-off is in, the version is ready to release. A sign-off can be required from another contributor, anyone holding an organization role such as IT Security, a role on the owning team (falling back to an organization admin if nobody on the team holds it), any member of a named team, or specific people, and a rule can require several distinct sign-offs. Whoever pushed the version never counts toward their own.

Blocked versions and overrides

A level’s review can block versions instead. A blocked version ships only if the tag is wrong and removed, or someone with the override permission picks Override and release. Keep it blocked is the other choice, and both need a written reason, recorded on the review.
Review of a blocked version with a banner explaining why, the version summary, an override form that requires a justification, and the sign-offs, tags and activity in the sidebar

A version blocked by its level, releasable only by override with a written reason.

Checks

Each automation flow that ran on a pushed version shows as a check: passed, running, waiting or failed (each with why), or cancelled. Checks link to their run with Retry failed, Re-run and Cancel, and authors answer an agent’s questions right on the review. Merging into main waits while checks are running or one has failed. Someone allowed to override can merge anyway with a reason, and the review records the reason and who merged.
Pending review with one failed check offering Retry failed and Re-run, and a merge box asking why to merge before the checks pass

Every sign-off is in, but a failed check holds the merge.

Deploying after review

Only versions that passed review, or didn’t need one, can be deployed.