Team and approval
Catch the wrong post before it goes live
The person drafting and the person publishing do not have to be the same. Role-based permissions decide who can approve what.
- Aren· EditorSubmitted for review14:20
Q4 launch teaser is ready — could you take a look?
- Selin· ReviewerRevision requested14:45
Visual lands well — let's tighten the last line.
- Aren· EditorResubmitted15:10
- Selin· ReviewerApproved15:20
Why it matters
Catch errors before publishing
Content enters the approval queue. Rejected posts go back with feedback — wrong posts never go live.
Role-based permissions
Viewer, Editor, Admin and Owner are hierarchical. Decide who approves what, per workspace.
Multiple workspaces
A separate space per brand or client. Accounts, posts and analytics never bleed between them.
How it works
- 1
Set up the workspace
Create a separate workspace per brand or client. Accounts, posts and analytics never bleed between them.
- 2
Assign the roles
Viewer, Editor, Admin and Owner are hierarchical. Editors draft; approval sits with the roles above them.
- 3
Route it through approval
Drafted content lands in the approval queue. It cannot publish unapproved, and a rejection goes back to the author with feedback.
Frequently asked questions
Is approval mandatory?
No. Working solo you can schedule directly; the approval flow exists for teams.
Can someone hold different roles in different workspaces?
Yes. Roles are assigned per workspace, so the same person can be an Editor in one brand and a Viewer in another.
Is the permission only enforced in the interface?
No. Permissions are enforced server-side, so an action hidden in the UI cannot be performed by calling the API directly either.
Explore the rest
Start Your Social Media
Success Today
Like thousands of businesses, simplify your social media management with Postid.