Roles and permissions
Owner, admin, and member — what each role can do, and how workspace invitations work.
3 min read
A workspace has three roles. They are deliberately coarse: a permission model with twenty checkboxes is a permission model nobody configures correctly.
| Capability | Owner | Admin | Member |
|---|---|---|---|
| Read boards, roadmap, changelog | Yes | Yes | Yes |
| Post, comment, change post status | Yes | Yes | Yes |
| Create and delete boards | Yes | Yes | No |
| Publish release notes | Yes | Yes | Yes |
| Declare and resolve incidents | Yes | Yes | No |
| Invite and remove teammates | Yes | Yes | No |
| Create and revoke API keys | Yes | Yes | No |
| Change billing and plan | Yes | No | No |
| Delete the workspace | Yes | No | No |
Inviting a teammate
- 1
Open Settings → Team.
- 2
Enter their email and pick a role.
- 3
They accept from the emailed link.
The link signs them in and joins them to the workspace in one step — they never choose a password, and an invite that is never accepted grants nothing.
There is exactly one owner
Billing and workspace deletion are owner-only. Before the owner leaves the company, transfer ownership — an orphaned workspace needs a support ticket to recover.
Something unclear or wrong? Tell us — or post it on our board.