Team Workspaces
Roles, reviewers and shared drafts, so nothing goes out unreviewed.
Some people draft. Trusted people approve.
One person can be writer and editor. A team should not be: the moment two people can publish under the company's name, you need to know who checks what. A workspace gives you that separation. It holds your members and their roles, and routes every draft to someone allowed to approve it.
Four roles
| What they can do | Member | Reviewer | Admin | Owner |
|---|---|---|---|---|
| Create drafts with agents | Yes | Yes | Yes | Yes |
| Approve or reject team drafts | No | Yes | Yes | Yes |
| Approve their own drafts | No | Yes | Yes | Yes |
| Invite teammates | No | No | Yes | Yes |
| Change roles, remove members | No | No | Yes | Yes |
| Delete the workspace | No | No | No | Yes |
How review works
- A member's agent runs. Its draft lands as awaiting approval.
- It appears in a Needs your review panel at the top of the Publish Queue for every reviewer, admin and owner, with a preview and who wrote it.
- A reviewer reads it, edits if needed, and approves or rejects, one at a time or in bulk.
- Approved posts publish on the next scheduler run.
This is enforced on the server, not by hiding buttons. A workspace draft can only be approved by a reviewer, admin or owner of that workspace. A plain member cannot approve their own work.
Reviewers who belong to several workspaces see all their pending reviews together.
Route a review to one person
In a workflow, the Review step can notify any reviewer or be assigned to a specific teammate, so the product announcement goes to the product lead and the hiring post to the people team.
Who needs which plan
Creating a workspace is a Scale feature, and Scale includes 3 seats: you and two teammates. Only the owner needs Scale. Joining someone else's workspace is free on every plan, and reviewers keep working whatever their own plan is.
Invites, switching workspaces and how social accounts are shared are covered in Team workspaces & roles and Approvals.