Campaigns reference

The whole module at a glance — and straight answers to the questions that only come up at the worst moment.

Roles

Role	Can
Owner	Everything, plus archive, delete, and transfer ownership. Exactly one per campaign — transfer is the only way to change it.
Editor	Edit the brief and campaign details, run lifecycle steps, manage assets, channels, deliverables — and publish.
Contributor	Add deliverables and attach assets; edit only the deliverables they created.
Observer	Read everything, change nothing.
Brand admins	With Manage all campaigns, act as Owner on every campaign; View all campaigns reveals campaigns you're not on.

Statuses

Thing	States
Campaign	Draft → Planning → Live → Completed, plus Archived (terminal — the one exitless state). Reopen is the only way back from Completed, and it asks for a new end date. Status never changes by itself; every move is a person's explicit step.
Deliverable	To do · In progress · Done · Skipped (kept on the record). Any state can move to any other.
Post	Draft · Scheduled · Publishing… · Published · Failed · Cancelled · Retracted · Removed on {channel}.

Practical limits

Surface	Ceiling
Upload batch into a campaign	5,000 files (over it, the error names the maximum)
Channel batch changes	100 per batch
Instagram post	Single image, carousel up to 10, or a reel (JPEG for images)
Facebook Page post	One photo or one video, plus a link
Performance tab listing	200 most recent posts listed; totals always cover everything
Metrics collection	Decaying schedule; ends 90 days after publish

What happens when… people come and go

When…	What happens
The person who scheduled a post leaves the brand (or is deactivated) before it fires	The post never ships under their name. Every scheduled post re-runs the full pre-flight at its fire moment, as the person who scheduled it — a departed scheduler fails that check, so the post lands in Failed, loudly, for an active editor to re-schedule or retry (a retry re-points it to the person retrying). Nothing is silently lost, nothing ships as a ghost.
The campaign's owner leaves the brand	The campaign keeps working — editors keep editing — but ownership does not move by itself. Owner-only actions wait until a brand admin transfers ownership; the campaign is never left ownerless mid-transfer, because the new owner is promoted before the old one steps down.
A deliverable's assignee leaves	The assignment stays, with their real name still on it — history doesn't rewrite. The picker only offers current members, so the next edit naturally reassigns it.
Someone deletes their whole account	The records stay; the identity empties. Campaign history and the publishing ledger are permanent — the rows simply stop resolving to a name.

What happens when… time passes

When…	What happens
The campaign's end date passes	Nothing automatic — campaigns never move themselves. "Schedule ended" shows on the Overview until someone marks it complete.
A deliverable goes overdue	The row turns red. That's all — no reminder, no auto-change; deadlines here are visible, not enforced.
You complete a campaign with posts still queued	They still go out — a finished campaign may legitimately have tail posts, and the completion dialog tells you the exact count that will keep publishing. Archiving is the opposite: it cancels everything still waiting.
A scheduled post misses its slot	It's flagged under "N posts need attention" the moment its time passes — never silently lost, and never double-posted.
A licence expires before a far-out post fires	The pre-flight judges licences as of the moment the post will actually go out — at composing AND again at fire time — so an expiring licence blocks instead of shipping.

What happens when… things get deleted

When…	What happens
You delete a campaign	It's gone for good — no campaign trash. Every still-queued post is cancelled first (a deleted campaign must never keep publishing), participants are told, and the attached source files stay untouched in the library. What already shipped is never erased — the posting record survives in the platform's permanent history — but with the campaign gone there's no page left to browse it on, so export the record first if you'll want it.
You archive a campaign	Three things: still-scheduled posts are cancelled, the campaign becomes read-only history, and Archived is the one state with no way back. Published posts and their metrics are untouched.
You delete or skip a deliverable	Its queued posts are cancelled (cause recorded), one notification explains why — and anything already published stays in the Performance ledger under the deliverable's real historical name. Deletion closes links, never erases history.
You try to trash a file a running campaign uses	Refused — files behind a Planning or Live campaign are locked platform-wide (folders containing them too). Once the campaign is Draft, Completed, or Archived, the lock lifts.
A file behind a scheduled post lands in the trash anyway	The post fails loudly at fire time instead of shipping broken — restore the file and hit Retry.

What happens when… reviews and selections move

When…	What happens
The review approving your deliverable is reopened	The campaign notices immediately: the chip leaves Approved, and publishing closes until the new round approves. An approval always describes exact versions.
You swap a file after the review approved	Publishing blocks on drift — the approval covered what reviewers saw, not what's there now. Re-review, or remove the changed file from the post.
A deliverable was never reviewed	It can still publish — with a loud "ships without an approval record" warning, in the composer and in readiness. Warned, never blocked; blocked only by a bad review.
The selection your campaign came from is reopened or deleted	Nothing changes in the campaign — the handoff was a one-time copy with a lineage pointer, not a live wire.

What happens when… connected accounts change

When…	What happens
The person who connected your Instagram leaves	Nothing breaks. Connections belong to the brand, not the person — anyone who manages brand settings can verify, reconnect, or disconnect it.
The channel is disconnected before a scheduled post fires	The post fails loudly at its fire moment rather than shipping through a dead or different account — reconnect and retry.
Someone reconnects the channel to a different Page first	The post fails rather than shipping to the wrong account — every post is pinned at composing to the exact account it was written for.
Access is revoked on the Facebook side	The next check notices and marks the connection revoked in Branduals — and everyone managing brand settings hears about it. Webhooks trigger checks; they're never trusted blindly.
A user removes the app in Meta settings or files a data-deletion request	Deauthorize revokes their connections everywhere; data deletion goes further and anonymizes them — credentials and account identity blanked, while the audit skeleton (which channel, when, why) and your posting record's numbers stay.
You disconnect in Branduals	Stored credentials are erased on the spot. Nothing is revoked on the platform side — that would break other channels riding the same person's grant.

What happens when… the plan changes

When…	What happens
Your trial or subscription lapses mid-campaign	You keep full read access — campaigns, Performance, the record export all stay open — and lose all writing. Scheduled posts do not fire while lapsed (the pre-flight's first check is an active plan); reactivate and retry, and they're waiting where you left them.
You're lapsed but posts are already live	Metrics keep collecting — deliberately. The performance curve is the record's identity; it doesn't get holes because billing hiccupped.
You downgrade to a plan without Campaigns	The module leaves the interface, but already-scheduled posts still fire and metrics still collect — a paid plan is a paid plan. The pages come back when the plan does.
You want out of the connected accounts after a lapse	Always possible — viewing and disconnecting your channel connections deliberately works on any plan state. You can always leave.

What happens when… AI agents are involved

When…	What happens
An agent works on campaigns	With campaign scopes granted, an agent can create and edit campaigns and deliverables, hold a campaign role, be an assignee, read readiness (exactly a preparing agent's fix-list), and read performance.
An agent tries to publish or connect an account	Never — by identity, not by permission. Publishing, scheduling, retracting, and account connections are human-only acts; no grant, role, or configuration opens them to an agent.
You review the activity trail	Every entry is marked person, agent (with "on behalf of {name}" when delegated), or system — you can always tell who — or what — did what.

Notifications

Fifteen kinds, in your language: campaign activated / completed / reopened / archived / deleted; added to a campaign; deliverable assigned or completed; a post failed, couldn't be confirmed, or was removed on the platform; scheduled posts cancelled by a cascade (with why); a connection stopped working; a live post's licence lapsed; and campaigns launching soon, in the Hub.

Availability

Campaigns is included in plans that carry the Campaigns capability — see pricing for current plans. Trial brands get the full module. Publishing to Facebook and Instagram is rolling out and currently runs for early-access brands while platform review completes.