Peer review lets you separate the person who builds a change from the person who approves it. When it's on, no one can push their own work live. A teammate has to review and approve the branch first. This is a simple way to add a second set of eyes before anything reaches your live, production workflow, and it applies to every change in a branch, including a step's code, config, and container image.
This article covers turning peer review on for a space, sending a push request as the author, and approving one as the reviewer.
How peer review works
Peer review is a space setting called peer-reviewed push live. When it's enabled for a space:
Anyone who created or edited a branch sees a 'Send push request' button instead of Push live.
They choose one or more reviewers, who get an email asking them to approve.
A reviewer opens the branch and clicks 'Approve'.
Once approved, the original author pushes the branch live themselves.
Note: Because review happens on the branch, the reviewer sees everything that changed, so there's no way for a particular change to skip review.
Turn on peer-reviewed push live
You need to be a manager of the space to change this setting. To turn it on:
Open the space's settings and go to the settings tab.
Find the Peer-reviewed push live card.
Toggle it on.
Once it's enabled, anyone who worked on a branch in that space will no longer see Push live for their own changes. They'll be prompted to request a review instead. To turn it off again, return to the same setting and toggle it off.
Read more about managing spaces here.
Send a push request (as the author)
When peer review is on and you've made changes worth publishing, a Send push request button appears in the branch selector where Push live usually sits. Selecting it opens a picker so you can choose who to ask.
The picker shows only the people who are allowed to approve, which means space members (directly or through a group) who have the push-live permission, excluding you, the branch's owner, and anyone else who contributed to it. From there you can:
Start from a suggestion. Anyone who recently pushed this workflow live appears first, so the obvious reviewer is a click away.
Search for someone specific. Find a person by name or email when you have one in mind.
Pick one or more reviewers. Only the people you select are emailed.
In a small space, where three or fewer people are eligible, everyone is selected by default so your request still reaches all of them.
After you send the request, the button changes to 'Request sent'. The people you picked receive an email with a link to the branch. You can cancel the request at any time before it's approved by selecting Request sent again.
Approve a push request (as the reviewer)
If someone asks you to review their branch, you'll get an email with a link to it. Open the branch, look over the changes, and when you're happy, select the 'Approve' button in the branch selector.
Note: Approving doesn't push the branch live. It unlocks pushing for the author, who gets an email letting them know they can now publish it themselves. You need the push-live permission in the space to approve.
Guardrails worth knowing
Peer review is enforced, not just a convention. A few rules keep it meaningful:
No approving your own work. You can't approve a branch you created or contributed to, and you can't approve a request you sent.
Approval is pinned to a version. The approval applies to the exact state of the branch that was reviewed. If you make more changes after sending the request, the pending request is automatically canceled and you'll need to send a new one.
Service accounts can't review or self-publish. A service account can't act as a peer reviewer, so it also can't push live in a space with peer review enabled.
Review versus the automated change summary
Peer review is a human approval gate. It's separate from the automated change summary that 3B generates in the chat when a branch goes live, which describes what changed but doesn't gate anything. You can read about that in the branches article. Both can be in play at once: a reviewer approves the branch, the author pushes it live, and 3B posts a summary of what just shipped.
