Product

Campaigns and approvals

A Campaign holds the brief, the dates, the budget, the team and every Deliverable. Review runs inside it, as an ordered chain of stages with a required role and a deadline in hours.

Request a demoSee pricing
The 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.

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.

The Campaign creation wizard with Campaign Info complete and the Channel Selection step open: Social Media and Email selected, with the platform and email type options for each.

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.

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.
The Content tab of a Campaign: Deliverables grouped by channel, each showing its slot owners, how many slots are filled, and its status.

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.
The slots of one Deliverable on the Assembly Board: caption, video and hashtag slots, each waiting on its owner with a Send Reminder action, and the assigned writer and designer with their roles.
The Tasks board with To Do, In Progress, In Review and Done columns, each task showing its priority, due date, Brand and assignee.

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.
An Approval Workflow with three ordered stages, each with its role and deadline in hours: copy review in 24 hours, a claims check in 12 hours and brand sign-off in 48 hours, plus the owner auto-approve rule.

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.
The Approvals queue with three posts pending approval, all three selected: the Approve Selected and Reject Selected buttons with the selection count, and the Content, Platforms, Submitted and Actions columns.

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 three guardrails: a monthly spending cap for the Campaign set above zero, a list of allowed domains, and at least one destructive-action rule that applies to the Campaign.

The 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.
The Jira Integration page on the Linked Projects tab: the bidirectional sync description and one linked project, active, with View Issues, Sync and Unlink actions.

Questions

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.

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.

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.

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.

Whatever the Autopilot level allows, which defaults to Suggest Only. Raising it requires the Campaign's three guardrails: a monthly spending cap above zero, an allowed-domain list and at least one destructive-action rule. Tool calls default to human confirmation.

Put one Campaign through the chain

Book a walkthrough, or create a Workspace and run a Deliverable through a review stage.

Request a demoStart your free trial

Last verified .