Approvals & collaboration

Approvals turn the social pipeline into an agency-style review loop: a contributor drafts a post, submits it, and an approver signs off before it can go out. It sits between create and publish in the social loop, a draft leaves the composer, gets reviewed here, and only then reaches the planner & calendar to schedule or publish. Around that review, every draft carries a private comment thread, a full revision history, and live presence, so a whole team can work a single post together.

Before you start

• Drafting and submitting a post needs the manage_social permission. Approving or rejecting needs the separate can_approve_social permission, Owners and Admins always have both. See roles & permissions.
• Approval is a per-space switch. With Require approval before publishing on, a post must reach Approved before it can be scheduled or published. With it off, a draft can publish directly and this review flow is optional but still available. Turn it on in settings & automation.

The approval flow

 ┌───────────────── Request changes ─────────────────┐
 │                                                    │
draft / in-progress ──Submit──▶ Awaiting approval ──Approve──▶ Approved ──▶ scheduled · published
 ▲                                     │
 └─────────── Withdraw (author) ───────┘

1. Submit for approval, from a draft (or an in-progress or previously failed post), the author clicks Submit for approval. The post moves to Awaiting approval and the submitter is recorded on it.
2. Review, anyone with can_approve_social opens the post and either:

• Approve, moves it to Approved, ready to schedule or Publish now.
• Request changes, the reject path. It sends the post back to draft with an optional reason (the author sees it), so they can revise and resubmit.

3. Withdraw, changed your mind before a decision lands? The author can Withdraw their own pending post back to draft. Only the original author can withdraw it.

Every transition, submit, approve, reject, withdraw, writes an audit log entry, so who moved a post and when is always on record.

Comment on a draft

Open a post to reach its Comments panel, a threaded, team-only discussion attached to that draft:

• @mention a teammate, an agent, or BotFather. Mentioning a person sends them a notification; mentioning an agent or BotFather can pull an AI reply straight into the thread.
• Assign a comment to a teammate so they own that piece of feedback. They get notified too.
• Resolve a comment once it's handled, pin an important one to the top, react with an emoji, and attach files. Replies stay nested under the comment they answer.

See who's on it, presence

While a post is open, the composer shows an Also viewing row of avatars: the teammates looking at that same draft right now, refreshed continuously so two people don't unknowingly edit over each other. Presence is ephemeral, an avatar drops off about a minute after that person leaves the post.

Revision history

Your edits are snapshotted as you work (rapid saves within a few minutes fold into a single revision). Open History on a post to browse earlier versions, expand any row to diff it against your current draft or the previous revision, and Restore one to bring it back. Restore is safe: your current state is snapshotted first, so you can always undo it from the same drawer. History tracks the editorial fields, body, hashtags, first comment, schedule, and target platforms, and keeps the most recent revisions per post.

FAQ

Who can approve a post? Anyone with can_approve_social, Owners and Admins always, plus any member you grant it to. It's deliberately separate from manage_social so people can draft without being able to self-approve.

Can the author approve their own post? Only if they also hold can_approve_social. With required approval on, that permission is the whole gate, grant it narrowly.

What happens to a rejected post? It returns to draft with the reason attached. Edit it and submit again; there's no limit on review rounds.

Do comments post to Instagram, X, or the other networks? No. They're internal-only. See the note above.

We're a solo team, do we need this? No. Leave Require approval off and drafts publish straight from the composer; comments and history are still there if you want them.

Next

• Composer
• Planner & calendar
• Settings & automation
• Roles & permissions