An Approval Workflow is an ordered chain of review stages. Nothing reaches a platform until the chain has been satisfied.
Building a workflow
Open the approvals settings and create a workflow. Add stages in the order they should run. Each stage names the role that must act on it and a deadline in hours, which is the service level you expect from that stage.
Set the workflow on a single Brand when one client reviews differently from the rest, or as the Workspace default so every Brand inherits it. A Brand level workflow wins over the default.
Add auto approve rules for roles that do not need to be asked. A post created by someone who already holds the reviewing role can pass that stage without waiting on a second pair of eyes.
What runs through a workflow
Posts and media assets both flow through approvals. A post enters the chain when its author submits it for review from the composer, and it stays pending approval until the last stage is satisfied, at which point it becomes approved and can be scheduled or published.
Assets in the Media Library run through the same kind of review, so a photograph can be approved once and then used across posts and Campaigns without being re-reviewed each time. See Media Library.
Campaign Content Slots carry their own review layer on top of this. A Content Slot moves through submitted and in review before it is approved or rejected, and the Deliverable it belongs to is not complete until its Content Slots are. See Campaigns.
The approval queue
The queue lists everything waiting on you, with the stage, the deadline and who submitted it. Open an item to read it in context, then approve it, reject it, or request changes with a note saying what to fix.
Select several items and approve or reject them together when the queue is long and the items are alike.
Comments and history
Comment inline on the item under review and mention a colleague to pull them in. A rejection or a change request carries your note back to the author, and the full approval history stays on the item: who acted, at which stage, when, and what they said. That history is the record to open when someone asks why a post went out.
Deadlines and escalation
Every stage deadline is counted in hours from the moment the item reaches that stage. A pending approval that passes its deadline is escalated automatically, so work does not sit silently in a queue while a launch date approaches.
Watch the queue for escalated items first. If a stage escalates often, either the deadline is too short for the reviewing role or the stage belongs to a different role.
Approvals and Agents
An Agent can be assigned to a Campaign role the way a person can, and its work enters the same chain. Governance controls decide what an Agent may do before a human sees it, including whether a tool call needs confirmation. See The AI workforce and Roles and permissions.