Teams & review
Comment on the draft, not in a group chat. Approvals live next to the post they are about.
Feedback that arrives as a screenshot in Slack has to be transcribed back onto the post by hand, and that is where copy gets lost. Comments and approvals attach to the post itself, so the review, the decision, and the thing being decided on are in one place.
Roles, comments, and approvals on the post.
How it works
Team collaboration, step by step.
- 1
Invite the team
Owner, admin, or member. Roles control who can connect channels and bill.
- 2
Comment on the draft
Threaded comments on the post, resolvable when addressed.
- 3
Request review
Send a post for a decision instead of asking someone to remember.
- 4
Approve or send back
Approve, reject, or request changes — with the history kept.
Capabilities
What you get with Team collaboration.
- Three roles, not a permission matrix
- Owner, admin, and member. Enough to separate who can connect accounts and manage billing from who writes posts, without a settings page nobody understands.
- Comments that resolve
- A comment thread lives on the post and can be marked resolved once it is handled, so a long review does not leave you re-reading settled points.
- Explicit review decisions
- Request a review, then approve, reject, or request changes. The status and full history stay on the post, so "who signed off on this" has an answer.
- A workspace per client, one bill
- Each workspace keeps its own channels, posts, and members. One subscription covers the workspaces your plan allows, so an agency does not buy a seat per client.
Why comments belong on the post
The failure mode is familiar. Someone screenshots a draft, pastes it into a channel, and writes "second line reads oddly". Now the feedback exists in a different system from the post, and somebody has to carry it across by hand. Two rounds later nobody is sure which version is current.
Comments attach to the post. They thread, they resolve, and they are still there when you reopen the draft next week wondering why a line is phrased that way.
The review decisions
| Action | What it means |
|---|---|
| Request review | Ask for a decision. The post's status reflects that it is waiting. |
| Approve | Signed off. |
| Request changes | Sent back with comments, without rejecting the whole thing. |
| Reject | Not going out in this form. |
| Cancel | Withdraw a review request you no longer need. |
"Request changes" exists as a separate outcome from "reject" for a practical reason: most feedback is a tweak, and forcing a reviewer to choose between approving something they have a problem with and rejecting a post they mostly like produces bad data about what actually happened.
The status and history stay on the post, which is what makes an audit question answerable later.
Roles
- Owner — full control, including billing. Holds billing ownership unless it has been transferred.
- Admin — manage channels and members, no billing.
- Member — write, comment, schedule.
Deliberately three. A fine-grained permission system is a thing you configure once, misremember, and then debug when someone cannot do their job.
Billing ownership blocks departure on purpose. Someone holding the subscription cannot leave a workspace until it is transferred or the subscription is cancelled, so a workspace never ends up paying for nothing with nobody able to fix it.
A workspace per client
Each workspace has its own channels, posts, members, and calendar. Nothing crosses between them — every query is scoped to the active workspace, so a client's content cannot appear in another client's calendar.
One subscription covers the number of workspaces your plan includes. That is the difference that matters for agencies: you are paying for volume, not for a seat per client.
For handing a calendar to a client for sign-off without giving them a login, see client approval calendars.
Found this useful? Pass it on.
Questions
Frequently asked questions Everything the first evaluation usually needs.
- Can I invite teammates and control what they can do?
Yes. Invite members to a workspace as owner, admin, or member. The role controls who can connect accounts, manage members, and reach billing. Everyone can write and comment.
- How does the approval flow work?
Request a review on a post. A reviewer then approves it, rejects it, or requests changes. The current status and the whole decision history stay attached to the post.
- Can someone outside the team review a post?
Yes, through a share link. A named recipient can open a shared post or calendar and comment on it without a Postonus account, which is the usual shape of a client sign-off.
- How do teams and billing work together?
A subscription belongs to the billing owner and covers up to the number of workspaces your plan allows. A member cannot leave while they hold billing ownership — it has to be transferred first, so a workspace cannot be orphaned mid-cycle.
- Do comments notify people?
Yes, through in-app notifications, so a comment does not depend on someone happening to reopen the post.
- Is approval required before publishing?
It is a workflow you choose to use, not a lock. Requesting review is deliberate; a post nobody has been asked to review still schedules normally.
Keep reading
- Client approval calendarSend a client a link to their content calendar. They comment and approve in the browser without an account, and you revoke the link once the engagement ends.Read
- Activity logOne feed of what happened: every publish, every failure with the platform’s own error, and a one-click retry, for when a client asks about last Tuesday.Read
- Channel groupsSave the sets of channels you always publish to together and select them in one click, instead of re-picking eleven accounts every time you compose.Read