Approvals
Approvals are how content reaches a social account that doesn't trust the author yet. They come in two distinct flavors:
- Account approvals — created automatically when someone schedules to an account they can't publish directly. These are the enforcement layer: the post will not reach the network until the account's approver signs off.
- Peer reviews — a teammate you explicitly ask for feedback. Advisory only; a peer review never unlocks publishing.
Who needs approval for which account is decided by the account's sharing settings — see Sharing and permissions for the full matrix.
How a post gets routed
Say a member schedules a post to the company LinkedIn (or to a founder's managed account):
- Scheduling always succeeds. Instead of Scheduled, the variant lands in Awaiting approval — the schedule dialog marks gated accounts with "Will be sent for approval", and the toast confirms it was sent.
- An approval request is created and routed automatically — to the Admins for a company account, to the owner for a personal one. Trusted members of the account can also act on it. Everyone eligible is notified.
- Any one eligible approver decides. First decision wins; the request records who resolved it and when.
Approve flips the variant to Scheduled — if its time already passed (someone hit Post now), it publishes on the scheduler's next tick, within ~30 seconds. Reject or Request changes hands the variant back as a draft with your comment attached; the schedule time is kept so the author can fix and resubmit in one click — which routes a fresh request.
Post now on a gated account behaves the same way: it never publishes immediately, it routes — the author sees "Sent to the channel's approvers."
Authority is verified again the moment a post actually publishes. If someone's trust was revoked between scheduling and the scheduled time, their post re-routes to approval instead of going out. The check runs server-side in the publish pipeline, so it applies identically to the app, the REST API, and AI agents over MCP.
The Approvals page
Approvals in the sidebar opens the queue, with a badge showing how many requests are waiting on you. Each pending row shows the post (linked), the target account chip, who asked and when — plus Approve, Request changes, and Reject with an optional note. Filter tabs show resolved history.
You only see requests you can act on: requests for your own accounts, accounts you're trusted on, company accounts if you're an Admin — and peer reviews assigned to you. There is no admin-sees-everything view; a private post under review between two teammates stays their business.
You can also resolve requests from the Approvals section on the post detail page — account requests appear there as "Approval for @handle".
Peer reviews
The post detail pane's Peer review request is the lightweight flavor: pick any teammate, they get a notification, their verdict and note land on the post. Useful for copy checks and second opinions.
Two properties worth remembering:
- Inviting a reviewer grants them visibility into a private post — that's how you share a draft with one person without putting it on the org calendar.
- A peer approval is advisory. If the post targets a gated account, the account's own approval is still required.
| Status | Meaning |
|---|---|
| Pending | Waiting on a decision |
| Approved | Signed off — held variants for that account are released |
| Rejected | Sent back; variant returns to draft |
| Changes requested | Revise and resubmit |
Every decision is logged in the post's activity feed and in the target account's activity feed, with the full chain preserved: who wrote it, who scheduled it, who approved it.