How to manage social media as a team: roles, approval and who can publish
Social media gets harder the moment a second person touches it. Who posted that? Did anyone check the price? Why did it go out twice? This is how to split the work so everyone knows their part: who writes, who publishes, who approves, and how SPREVA keeps a record of all of it.
Rodolfo MotaFounder of SPREVA
The short version
Give each person the smallest role that lets them do their job: Editors write and send for review, Publishers schedule, an Admin manages accounts and people. Turn on approval so nothing goes out unseen, and invite clients or managers as Reviewers, who take no seat. Keep separate brands or clients in separate workspaces, and let the audit log answer who did what.
Seven roles, one job each
Every member of a workspace has one role:
| Role | What it can do |
|---|---|
| Owner | Everything, including billing, deleting the workspace and changing other owners |
| Admin | Manages members, social accounts, settings, API keys and webhooks; sees analytics and the audit log; can approve posts |
| Publisher | Publishes and schedules posts and manages queues |
| Editor | Writes, edits and deletes posts and media, but cannot publish or schedule |
| Analyst | Sees everything and the analytics; cannot change anything |
| Viewer | Sees posts, media, queues, accounts and members; cannot change anything |
| Reviewer | Approves posts or sends them back with a note, and sees nothing else |
Three common setups
Most teams look like one of these:
- A small business: the owner, and one Editor who writes the week's posts for the owner to publish.
- A marketing team: an Admin for the accounts, Publishers who run the calendar, Editors who write, and approval on.
- An agency: a workspace per client, the team in each, and the client as a Reviewer who approves their own posts. How to manage social media for several clients without posting to the wrong one.
Inviting the team
- 1
Open Team and press Invite.
- 2
Enter the person's email and choose their role. Someone who already has a SPREVA account joins at once; anyone else gets an invitation link.
- 3
The link works for 7 days and only for that email address. New link replaces it, Withdraw invitation cancels it.
- 4
Change a role at any time. When someone leaves, remove them: their API keys stop working with them.
Approval before anything goes out
In Settings, turn on Posts need approval before they go out. From then on:
- Posts are sent for review instead of scheduled, by Editors and Publishers alike. Reviewers approve them, or, if there are none, Owners and Admins do.
- A reviewer approves, or requests changes with a note, which sends the post back to its author as a draft.
- An approved post keeps its time. Editing it sends it back for review; moving only its time does not.
- Nobody approves their own post. Owners and Admins can schedule without review when they must, and it is recorded.
If nobody approves a post by its time, it does not go out: it becomes a draft again and its author is told. The client has not approved and the post is due: publish, hold or skip?.
Who connects the accounts
Only Owners and Admins connect social accounts and reconnect them when access runs out; everyone else is asked to tell an admin. Every role except Reviewer sees all the accounts in the workspace, so when people must not see each other's accounts, give each brand or client a workspace of its own.
Who did what
The audit log, for Owners and Admins, shows who did what in the workspace and when. Each post has its own activity, and an approved post keeps an approval record you can print: who sent it, who approved it, and what it said at that moment.
Two people, one post
If two people edit the same post and one saves first, the second save is refused with a message to reload, so nobody's work is overwritten in silence. The habit that avoids it: one person owns each post until it is sent for review.
Seats and plans
Starter includes 3 members, Pro 10 and Business 25, and pending invitations count. One person counts once across the workspaces you pay for. Reviewers take no seat, up to 25 per workspace on every plan.
Set up your team today
Invite your team with the smallest role each needs, turn on approval, and send the first post for review. Every plan starts with a 7-day trial. SPREVA for agencies.
Questions
Can an Editor schedule a post?
No. An Editor writes and sends posts for review; a Publisher, an Admin or an Owner schedules them.
Can someone approve their own post?
No. Another person always approves it.
Can I limit a member to some of the accounts?
Not inside one workspace: every member except reviewers sees all its accounts. Use a workspace per brand or client to keep them apart.
What does a client see as a Reviewer?
Only the posts waiting for them: a preview for each account, the full text, when it goes out and where, and what changed since they last saw it.
Written by
Rodolfo Mota
Founder of SPREVA
Makes SPREVA in Portugal: the Studio, the tools an agent works with, and the publishing behind them.
Keep reading
- One post from draft to feed: a client approval workflow, step by stepOne bakery post followed from the draft to the morning it goes out: who does what, what the client sees, and what happens when the answer is not yes.
- How to manage social media for several clients without posting to the wrong oneOne workspace per client, accounts that cannot cross, a free reviewer each and a plan each. How an agency keeps clients apart in SPREVA, and what it costs.
- The client never approved it, and it went out anywayA time moved, a caption fixed after the yes, a post scheduled in a hurry. How posts go out unapproved, and how SPREVA makes every post wait for a yes.
Can the team leave comments on a post?
Not yet. A reviewer's note when requesting changes is the one message attached to a post.