Team review

Review before render works on your machine today: a series with review on holds each job until a person approves it. Team review is the same step, with the person somewhere else. The job waits in a shared queue in the console, and a reviewer decides.

​

The queue

When your local project stops a job for review, it sends the script, the quality checks, and a preview frame to the organization’s Review queue. The console shows the queue with filters for waiting, approved, and rejected. Open an item to see the script, the checks, the preview frame, and the history of decisions. The sidebar shows how many items wait, to anyone who can decide.

​

Who decides

A reviewer has no other access. See Teams and roles. Approval is a person’s decision: a web session or a command-line sign-in. An agent connected through MCP cannot approve. To reject, the reviewer must give a reason. If two people decide at once, one decision wins and the other is told the item was already decided. A decided item is final. A changed script is a new item.

​

After the decision

Your project checks the queue and then acts on the answer:

• Approved: the job goes on to render. The usual publish rules still hold: never upload twice, dry-run until the series is live, and going live needs the typed channel id.
• Rejected: the job ends as rejected with the reviewer’s reason, as it does when you reject locally.

Rendering locally is unchanged. See Cloud rendering for rendering in the cloud.