✦ Team & Approvals

Nothing goes live before someone says so

Add your team and your clients with exactly the access each should have. Draft, review, approve — and give every seat its own AI allowance so adding a person adds capacity, not just a login.

Per-brand accessApproval before publishEach seat adds allowance

Free plan · No credit card required · Cancel any time

Active rules

Inquiry

DMs · Reply to all

Data Viz

Comments · keywords

Price · cost

Comments

Works across every channel you publish to

$0

Per seat, per month

$89 billed annually

0

Generations per seat

Added to the shared pool

0

Credits per seat

Every month, shared

0

Roles

Approver, editor, view-only

✦ A quick tour

Who can do what, and when

Three views of the same workflow.

✦ Roles

Access granted brand by brand

A freelancer on two of your twelve clients sees exactly those two. Roles are scoped to the brand rather than the account, which is the only version of permissions that survives a growing roster.

Active rules

Inquiry

DMs · Reply to all

Data Viz

Comments · keywords

Price · cost

Comments

Collaboration without the shared password

Most small teams still run social from one login and a group chat. It works until it does not.

✦ Approvals

The review step that actually gets used

Approval only works if it is on the path rather than beside it. A post that needs sign-off cannot publish without it, sits visibly in the queue, and releases the moment the right person says yes.

  • Drafts held until an approver releases them
  • Who it is waiting on, visible in the queue
  • Approval mode available for auto-reply rules too

Up next

Product launch reel

Today · 9:00 AM

Auto

Customer story thread

Tue · 6:30 PM

Auto

Behind the scenes

Wed · 8:00 PM

Auto
✦ Client sign-off

Let the client approve their own posts

The neatest way to end the email-a-spreadsheet review cycle. Add the client to their own brand as an approver — they release their posts and read their own numbers, and see nothing belonging to anyone else.

  • Clients added per brand, never account-wide
  • Approver, editor or view-only as it suits
  • Their calendar and reports, nobody else's

Content calendar · August

SMTWTFS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
✦ Seats

A seat adds capacity, not just a login

Every teammate brings 300 AI generations and 300 credits a month into the shared pool. Hiring a second person does not mean rationing the first one's allowance.

  • 300 extra generations per seat, every month
  • 300 extra credits per seat, shared across brands
  • Credits can be gifted between owner and teammates

Recent activity

@sarok

Auto-replied to a comment

just now

@farhan

DM answered · Greeting

2m

@meta_user

Comment hidden · spam

5m

✦ The full set

Everything a team needs

And nothing that requires a shared password.

Approval workflow

Posts held until the accountable person releases them, with the waiting list visible to everyone who needs it.

Roles & permissions

Approver, editor or view-only, per brand.

Per-brand membership

Access to the clients they work on, and no others.

Client approvers

Let the client sign off their own calendar.

Seat allowances

Each seat brings its own AI generations and credits.

Credit gifting

Move credits from the owner to whoever needs them.

Activity log

Published, approved, replied — with a name attached.

Work stays with the brand

Removing a seat removes access, not the drafts, schedule or history. Nobody rebuilds a calendar because somebody left.

Up and running in three steps

  1. Step 01

    Invite the people

    Teammates and clients by email. Each seat is added to the brands they actually work on.

  2. Step 02

    Give each a role

    Approver, editor or view-only — per brand, so nobody gets more reach than the job needs.

  3. Step 03

    Turn approvals on

    Drafts then wait for sign-off before publishing, and the queue shows who they are waiting on.

The review cycle, without the email chain

A presenter standing at a screen addressing colleagues seated with laptops around a boardroom table
Approvals before anything goes live
A group working together on laptops around a long table in a bright, wood-panelled room
Your whole team, one inbox
Three colleagues talking beside their desks in a bright open-plan office
Hand off to a human whenever it matters

The difference it actually makes

One shared login

  • A password in a group chat that nobody rotates
  • Approvals living in an email thread and a spreadsheet
  • No way to tell who published the post everyone is asking about
  • A leaver still holding access a month later

With team and approvals

  • Individual seats, scoped brand by brand
  • Sign-off on the publishing path, not beside it
  • An activity log with a name against every action
  • Remove a seat and the work stays where it was

An approval step that lives in an email thread is not an approval step.

Here a post that needs sign-off cannot publish without it — and everyone can see what it is waiting on.

Questions, answered

Which plan includes team features?

Agency. Free and Pro are single-operator plans — Pro gives one person three brands and the full AI toolkit, but team members, roles and approval workflows start on Agency.

What does a seat cost?

$99 per user per month on top of the Agency plan, or $89 on annual billing. Each seat brings its own 300 AI generations and 300 credits a month into the shared pool, so a seat adds capacity rather than just access.

Can a client approve their own posts?

Yes, and it is the tidiest way to run sign-off. Add them to their own brand as an approver — they can review and release their posts, see their own numbers, and have no visibility of any other client.

Does approval apply to auto-replies too?

It can. Auto-reply rules have an approval mode that queues generated replies for a human to release, which is the sensible way to run the first week of any new rule before letting it go on its own.

Can somebody have access to one brand but not another?

Yes — membership is granted per brand, not account-wide. A freelancer working on two of your twelve clients sees exactly those two.

What happens to a teammate's work if I remove them?

Their drafts, scheduled posts and history stay with the brand. Removing a seat removes access, not the work — you are never left reconstructing a calendar because somebody left.

Give everyone the right amount of access.

Set up your team on Agency, with a seat allowance that grows as the team does.