The review process
Review is how your team keeps brand work on-brand. Work starts as a draft. When it’s ready, someone submits it. A brand Manager opens the brand’s Review queue, steps through the pending items, and either approves each one or sends it back. Approved work is locked as final; work sent back goes to the Creator for another pass.
The status words you’ll see are plain: Draft, In review, Approved, Changes requested, and Retired.
The flow at a glance
Section titled “The flow at a glance”- A Creator makes an image or video on a brand. It starts as a private Draft: only the Creator and the studio’s owners and admins can see it. An upload starts as a Draft the whole brand team can see.
- The Creator submits it for review. The status becomes In review and the brand’s Managers are notified.
- A Manager opens the brand’s Review queue, steps through the pending work, and either approves an item or requests changes on it.
- Approved work is final and locked. Work marked Changes requested returns to the Creator, who can revise and resubmit.
Roles decide who does what: Creators submit; brand Managers and Approvers decide. Where this page says Manager, an Approver (often a guest) can make the same decision. See Members & roles for what each brand role can do, and Brands for how brands are set up.
Submitting work for review
Section titled “Submitting work for review”Open the item you want reviewed. While its status is Draft, you’ll see Submit for review. Click it.
The status changes to In review, and every Manager on that brand gets a notification. Submitting a private draft also shares it with the brand, since its reviewers need to see it. While an item is In review, it’s waiting on a decision — you don’t need to do anything else.
The Review queue
Section titled “The Review queue”Review happens inside the brand. Open Review in the sidebar and you land on the queue for the brand you’re working in; the count beside it is that brand’s. You can also open the brand and pick its Review tab.
The queue has three parts:
- On the left, the work waiting for a decision, grouped by project.
- In the middle, the asset you’ve picked: the full image or a video player.
- On the right, the panel with Approve and Request changes.
Switch the filter to Changes requested to see what you’ve sent back and the note that went with it. That view is for reading only, so it has no decision buttons.
The filter and the asset you have open stay in the page link. Reload and you’re back where you were, or copy the link to send a teammate straight to the same asset.
When the queue is empty, you stay on the brand and see what to do next.
Reviewing an item
Section titled “Reviewing an item”Pick an item on the left and decide from the panel on the right:
- Approve marks the item Approved and final.
- Request changes sends it back to the Creator. Add a note first; the Creator sees it.
After each decision the queue moves on to the next item that still needs one, so you can clear the brand’s queue without hunting for what’s left. To talk an item through before you decide, use its Thread tab. See Threads & comments for how mentions and replies work.
You can also decide from the full-window viewer in the Library. While a file is in review, the status line under its name has Approve, and Request changes is in the ⋯ menu. In the viewer, Enter approves and R requests changes, and ? lists every shortcut. See The next step for the details.
On a phone
Section titled “On a phone”On a phone the Review queue has a Review N button above the grid. Tap it to open the first file full screen, with Request changes and Approve along the bottom.
- Approve moves straight to the next file. An Approved · Undo notice stays up for five seconds; tap Undo to put the file back in review. The approval is sent when the five seconds run out, when you approve the next file, or when you close the viewer.
- Request changes opens Comments with the reply box ready. Write what should change and tap Request changes: the note is posted to the file’s thread, the file moves to Changes requested, and the next file opens. You can’t send it empty.
- Swipe left or right to look at other files without deciding.
When every file has a decision you’ll see All caught up, with a count of what you approved and sent back.
Keyboard shortcuts
Section titled “Keyboard shortcuts”The Review tab works from the keyboard:
| Key | Action |
|---|---|
j or ↓ | Next item |
k or ↑ | Previous item |
a or Enter | Approve |
r or n | Request changes |
Esc | Cancel the note, or clear the ticked assets |
Shortcuts pause while you’re typing, while the Thread tab is open, and while assets are ticked, so a comment or a selection never triggers a decision by accident.
Review many assets at once
Section titled “Review many assets at once”To decide on a batch, tick several assets in the queue, or tick a whole project at once. A bar appears at the bottom with Approve and Request changes for everything you’ve ticked.
- Approve approves them all. If the brand posts reviews to Slack, you get one message for the brand instead of one per asset. See Slack.
- Request changes sends them all back, with one note that goes to every creator involved.
Press Esc to clear the selection.
What the statuses mean
Section titled “What the statuses mean”| Status | What it means |
|---|---|
| Draft | Not yet submitted, not final. A new generation is private to its creator until it’s shared; an upload is visible to the brand team. |
| In review | Submitted and waiting on a Manager’s decision. |
| Approved | Accepted and locked as final. |
| Changes requested | Sent back to the Creator to revise and resubmit. |
| Retired | Taken out of circulation with Retire. It stays in the Library, and Unretire puts it back to draft. This used to be called Archived. |
After a decision
Section titled “After a decision”Approved work is final and locked. You can’t edit an approved item in place. To change it, open it and choose Edit / Fork — this makes a fresh draft copy you can rework and submit for review on its own. The original approved version stays untouched as a record.
Work sent back goes to the Creator. They’ll see your note, make changes, and submit the revised version for review again. There’s no limit on revisions.
When you’re the only reviewer
Section titled “When you’re the only reviewer”If nobody else on a brand can approve, waiting for review would mean waiting forever. So when you’re the only reviewer, your drafts show Approve straight away in place of Submit for review, both in the viewer and in the bulk bar. Submit for review is still there in the ⋯ menu if you want the item in the queue anyway.
As soon as someone else on the brand can review, drafts go through review again.
Self-approval
Section titled “Self-approval”When the brand has other reviewers, you can’t approve your own submission by default: someone else has to sign off. When you open one of your own items, the Approve button is off and a notice explains why.
A brand can turn on self-approval. With it on, a Manager’s own work is approved automatically and skips the wait. A studio admin or brand Manager sets this in the brand’s settings. See Brands for where to find it.
Notifications and history
Section titled “Notifications and history”Review keeps your team in the loop:
- Submitting work notifies the brand’s Managers.
- Approving or requesting changes notifies the Creator, with your note attached.
- @-mentioning someone in a Thread notifies them directly.
Every submission and decision also shows up in the Activity feed, so anyone on the brand can follow how work is moving. If an item belongs to a project, the queue groups it under that project, and a chip in the viewer names it while you review. An item in several projects shows one name and +1 (or more); click the chip to see them all.
Reviewing from Slack
Section titled “Reviewing from Slack”If your studio has added Cauldron to Slack and the brand has a review channel set, submitted work also posts to that Slack channel with the asset attached. The message carries Approve and Request changes buttons, so a reviewer can decide without opening the studio — Request changes opens a dialog for the feedback note, which is required there. After a decision the Slack message updates in place with who decided and when.
Comments sync both ways: a thread comment on the asset mirrors into the Slack thread under its review message, and a reply in Slack lands back on the asset in the studio, attributed to whoever wrote it. Connect your own Slack account from your profile first, so decisions and comments map to your studio account. People outside your studio on a Slack Connect channel can reply in the thread without an account, but only studio members with the right brand role can approve or request changes. See Slack for setup, permissions and troubleshooting.