The review process
Review is how your team keeps brand work on-brand. Work on a team brand starts as a private draft. When it’s ready, someone submits it. A brand Manager opens the 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 Archived.
The flow at a glance
Section titled “The flow at a glance”- A Creator makes an image or video on a team brand. It starts as Draft — visible to the team but not yet final.
- The Creator submits it for review. The status becomes In review and the brand’s Managers are notified.
- A Manager opens the 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 decide. 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. While an item is In review, it’s waiting on a decision — you don’t need to do anything else.
Work on your Personal brand skips review entirely. There’s no submit step and no queue; Personal-brand items are yours alone. Review only applies to team brands.
The Review queue
Section titled “The Review queue”Open Review in the sidebar. The page is titled Review queue.
You see a card for each brand you can review, with a count of items waiting. A brand with nothing pending reads All clear. Click Open queue on a brand to load its pending work into a gallery below — a grid of every item awaiting a decision, oldest first.
If you don’t manage any brands, the queue tells you so and points you to your studio admin.
The queue opens brand-first on purpose: you pick a brand, then focus on that brand’s pending work without other brands in the way.
Reviewing an item
Section titled “Reviewing an item”Click any item in the gallery to open the focused viewer. It fills the screen with two panes.
On the left is the media — the full image or a video player — with a filmstrip of the whole queue along the bottom. Click any thumbnail to jump to it, or use the arrows to step forward and back. As you decide on items, the filmstrip marks them so you can see what’s left at a glance.
On the right are two tabs:
- Info — the details of the item: the model used, any campaigns it’s tagged with, the prompt, and a Note (optional) field for feedback.
- Thread — the item’s conversation. Leave a note, ask the Creator a question, or read earlier feedback before you decide. See Threads & comments for how mentions and replies work.
Approve or request changes
Section titled “Approve or request changes”At the bottom of the Info tab:
- Approve marks the item Approved and final.
- Request changes sends it back to the Creator. Add feedback in the Note (optional) field first — the Creator sees your note.
The viewer keeps you moving: after each decision it advances to the next item that still needs one, so you can clear a queue without leaving your seat.
Keyboard shortcuts
Section titled “Keyboard shortcuts”The viewer is built for fast, hands-on-keyboard review. While the Info tab is open:
| Key | Action |
|---|---|
j | Next item |
k | Previous item |
a | Approve |
r | Request changes |
n | Jump to the note field |
Esc | Close the viewer |
Shortcuts pause while the Thread tab is open, so typing a comment never triggers a decision by accident.
What the statuses mean
Section titled “What the statuses mean”| Status | What it means |
|---|---|
| Draft | Created on a team brand, not yet submitted. Visible to the team, not final. |
| 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. |
| Archived | Set aside out of the active flow. |
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.
Self-approval
Section titled “Self-approval”By default, you can’t approve your own submission — a different Manager 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 items belong to a Campaign, you’ll see that tag right in the viewer while you review.
Reviewing from Slack
Section titled “Reviewing from Slack”If your studio has Slack connected, submitted work also posts to a 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 settings first, so decisions and comments map to your studio account.