Members and roles
Every workspace member has one of three roles: Owner, Admin, or Member. The person who created the workspace is its Owner; everyone else joins as Member or Admin via invitation.
Roles are deliberately coarse — they govern workspace administration. What you can do with a specific post or social account is governed by sharing and permissions: post visibility, account kinds, and per-account trust. The short version: Admins run the workspace and its company accounts, but have no special powers over members' personal accounts or private posts.
What each role can do
Every member (any role) can use WriteMars as their own tool: create posts (private by default), connect their own social accounts, schedule and publish to them, and browse everything shared to the org — the org calendar, company accounts, states, labels, campaigns, the People directory, and public writing skills.
Editing follows visibility plus one rule: within the posts you can see, any member can collaborate on content and schedules — the per-account gates decide whether a schedule publishes directly or routes to approval. Deleting a post or changing its details remains creator-or-Admin.
| Capability | Member | Admin | Owner |
|---|---|---|---|
| Create posts, variants, labels, states, campaigns | ✓ | ✓ | ✓ |
| Edit own People profile and own skills | ✓ | ✓ | ✓ |
| Read/use public skills | ✓ | ✓ | ✓ |
| Moderate another member's public skill | — | ✓ | ✓ |
| Connect & manage own social accounts | ✓ | ✓ | ✓ |
| See private posts outside their audience | — | — | — |
| Connect / manage company accounts, post to them directly | — | ✓ | ✓ |
| Propose posts to company accounts (→ approval) | ✓ | ✓ | ✓ |
| Schedule to managed personal accounts (→ owner approves) | — | ✓ | ✓ |
| Resolve approvals | own/trusted accounts | + company accounts | + company accounts |
| Invite members, revoke invitations | — | ✓ | ✓ |
| Change member roles, remove members | — | ✓ | ✓ |
| Update workspace settings | — | ✓ | ✓ |
| Delete the workspace | — | — | ✓ |
| Leave the workspace (remove self) | ✓ | ✓ | — |
A blocked action returns "Access denied" in the app and 403 forbidden over the API; a post outside your audience is simply a 404. Tokens and MCP agents carry the same permissions you have in the app.
Admins publish directly to every company account and approve anything routed to one. In a 50-person workspace that should be two or three people — everyone else collaborates through proposals and per-account trust.
Invite people
From Settings → Members, switch to the Invitations tab and click Send invites:
- Add one or more rows of Email + Role (Member or Admin — Owner can't be granted). Duplicates in the list are sent once.
- Click Send invites. Each person gets an email with a join link.
Re-inviting an email that already has a pending invitation doesn't send another email; if you picked a different role, the pending invitation's role is updated.
Invitation lifecycle
An invitation is pending until the person responds, then becomes accepted or declined — the Invitations tab shows the status of each. While pending, you can revoke it (it stops working immediately).
On the invitee's side: sign in (or sign up) with the invited email address, and the invitation appears on the Workspace invitations screen (/workspace/invites, also reachable from the workspace switcher) — select and Join selected. Invitees join with the role on the invitation.
Change roles and remove members
On the Members tab of Settings → Members, Admins and Owners can:
- Change a role — the dropdown next to each member switches between Member and Admin. The Owner's role can't be changed.
- Remove a member — the trash icon. The Owner can't be removed.
Anyone can remove themselves (leave the workspace) — except the Owner.
Their People profile and every private or public skill they owned in this workspace are permanently deleted. Removal is also retroactive for delegation: posts they scheduled to gated accounts re-route to approval instead of publishing, and their pending auto-engagement rules stop. If the departed member owned a personal account with requests still queued, those requests fall back to the Admins so nothing is stranded.