How many review stages can a workflow have?

The chain is an ordered list you define, stage by stage. Each stage names a required role and a deadline in hours, and the workflow applies to one Brand or to the whole Workspace as a default.

What happens when a reviewer misses the deadline?

A pending approval past its hour deadline is escalated automatically. The item stays in the queue with its history intact, so the next reviewer sees what was asked and what changed.

Can clients review inside Collabre?

Yes, as reviewers in an Approval Workflow with in-app roles and accounts. Every comment, change request and decision stays on the item, with the full approval history.

Do assets go through approval too?

Yes. The approval chain runs on posts, on Campaign Content Slots and on media assets, so a new version of a file is signed off before it ships. Assets keep version history with an active-version pointer as well.

What can an Agent do on a Campaign without me?

Whatever the Autopilot level allows, which defaults to Suggest Only. Raising it requires the Campaign's guardrails: a monthly spending cap and an allowed-domain list. Tool calls default to human confirmation.

Campaigns and approvals

Screenshot pendingThe Campaign detail page for a Campaign in the Production phase, Overview tab selected: the Campaign name, the interactive phase bar with Setup, Planning, Production and Launch, the tab row showing Overview, Content, Analytics, Attribution, Team and Activity, and the brief panel.

The Campaign container

A Campaign carries a brief, goals, a budget, a date range, assigned members with defined roles, a set of Deliverables and the phase it is in. Its lifecycle runs Setup, Planning, Production, Launch, with an interactive phase bar showing where the Campaign stands and what remains. Posts, tasks and assets attach to the Campaign, and performance rolls up to it.

Complete a phase from the phase bar and move the Campaign on.
Attach posts, tasks and assets to the Campaign they belong to.
Read goal tracking, attribution and the change-history timeline on the Campaign itself.

The creation wizard

A guided setup builds the Campaign panel by panel and saves a draft as you go. The panels are grouped by phase, Setup first and then Planning, and each carries a required, recommended or optional badge, so a Campaign can be created before the optional panels are filled in.

Setup:

Campaign Info: name, dates, color and description.
Channel Selection: the channels this Campaign covers, from Social Media, Email, Paid Ads, Blog / CMS, SMS / Push and Influencer.
Brief & Goals: target audience, key messages and KPIs.
Reference Assets: upload brand guides, mood boards and other references.
Budget Allocation: set the budget per channel.

Planning:

Deliverables Definition: define the content items owed, per channel and platform.
Content Calendar: place the Deliverables on a timeline.
Team Assignment: assign the roles, and the people or Agents filling them.
Marketing Checklist: track steps from a template or as custom items.

Screenshot pendingThe Campaign creation wizard, a draft in progress with the Setup steps complete and the Deliverables step expanded: the step list with its required, recommended and optional badges, the completed and in-progress status icons, and the expanded Deliverables panel.

Deliverables and Content Slots

A Deliverable is one finished item the Campaign owes, such as an Instagram launch post. It breaks into typed Content Slots: caption, image, video, thumbnail, hashtags, first comment, alt text, ad copy and more. Each slot is assigned to a Writer, Designer or Reviewer role, and each slot runs its own lifecycle: Empty, In Progress, Submitted, In Review, then Approved or Rejected.

Define the Deliverables a Campaign owes, per channel and platform.
Assign every Content Slot an owner role.
Submit a slot from the Composer and watch it move into review.

Screenshot pendingThe Content tab of the Campaign detail page for a Campaign with Deliverables grouped by channel and slots in mixed states: the Deliverable groupings, the typed Content Slots under one Deliverable, the role on each slot, and the slot status labels.

The Assembly Board and the contributor view

The Assembly Board composes a Campaign's Deliverables and their Content Slots into the finished piece, with platform previews of the assembled result. People in non-manager roles get their own view instead: a dashboard of only the slots assigned to them, filtered by To Do, In Progress and In Review, with overdue and due-this-week counts.

Compose the slots of a Deliverable and read the platform preview.
Work your own queue on My Tasks without opening the whole Campaign.

Screenshot pendingThe Assembly Board for a Campaign in the Production phase with at least three Deliverables and slots in mixed states: the Deliverable groupings, several Content Slots with different states side by side, one assembled platform preview, and the Campaign name in the header.

Screenshot pendingThe contributor dashboard for a contributor with slots across several Campaigns, the All filter selected: the My Tasks heading, the All, To Do, In Progress and In Review filters, the overdue and due-this-week badges, and the task list with the Campaign each slot belongs to.

Approval Workflows

An Approval Workflow is an ordered chain of review stages. Each stage names the role required to sign off and a service-level deadline in hours. Workflows are set per Brand, or Workspace-wide as a default. Auto-approve rules can be set for named roles, and a pending approval past its deadline is escalated automatically.

Order the stages and name the role that signs off on each one.
Give each stage its deadline in hours.
Set the workflow on a Brand, or as the Workspace default.
Add auto-approve rules for the roles that do not need to review.

Screenshot pendingApproval Workflows with one saved workflow of at least three ordered stages: the stage order, the role on each stage, the hour deadline on each stage, and the scope showing which Brand the workflow applies to.

The review queue

Everything waiting on a decision sits in one queue. Select several items and approve or reject them together. Comments carry @mentions, change requests and the full approval history, so the reasoning stays on the item rather than in an inbox. Campaign Content Slots carry their own review layer on top. Media assets run through the same chain, so an image is signed off before it ships.

Select several items and approve or reject them in one action.
Leave a change request with an @mention on the item itself.

Screenshot pendingThe Approvals queue with several posts pending approval and three of them selected: the Approvals page header, the Approve Selected and Reject Selected buttons with the selection count, and the table columns Content, Platforms, Submitted and Actions.

Autopilot and spending caps

Each Campaign carries an Autopilot level, a dial that decides how far Agents may act without asking: Off, Suggest Only, Auto with Approval, Full Auto. It defaults to Suggest Only, so an Agent proposes and a person decides. Promotion above Suggest Only requires guardrails: a monthly spending cap for the Campaign and a list of allowed domains.

Set the Autopilot level for this Campaign.
Give the Campaign its monthly spending cap before raising the dial.
List the domains Agents on this Campaign may reach.

Screenshot pendingThe Campaign Autopilot page with Suggest Only selected and the guardrails partly satisfied: the four Autopilot levels with their descriptions, the guardrail checklist, the monthly spending cap field and the allowed-domains field.

Tasks, checklists and Jira

Production work sits next to the content it produces. Tasks carry configurable statuses, subtasks, labels, priorities, assignees, due dates and blocker relationships, and they link to Campaigns, Deliverables and Content Slots. Marketing checklists attach to a Campaign so setup steps are not skipped. Teams that keep Jira as their system of record get two-way issue sync, epic-to-campaign linking and workflow mapping.

Link a task to the Deliverable or Content Slot it produces.
Define your own board columns rather than accepting fixed ones.
Keep Jira in sync in both directions, and link an epic to a Campaign.

Screenshot pendingThe Jira integration dashboard for a connected Jira site with issues synced: the Jira Integration heading with its bidirectional sync description, the synced issue list, and the epic-to-campaign links.