Get started
Invite your team
How to add people to a workspace, what each of the four roles can do, when to make your own, and who is allowed to invite or remove whom.
Everyone in a workspace holds exactly one role, and that role decides what they can do. There are three built in, and they are the same in every workspace.
The three roles
| Role | For |
|---|---|
| Owner | Runs the workspace, members, roles, billing, and settings. At most two |
| Admin | Day-to-day administration, settings and members |
| Member | The standard role for someone doing the work |
One person holds one role per workspace. If someone needs different access in a different workspace, that is a separate membership with its own role.
When three is not enough
If a role you need sits between two of these, a bookkeeper who should see billing but not manage members, say, an Owner can create a custom role with exactly the permissions it needs. Custom roles are offered alongside the built-in ones when you invite someone. Make one when you find yourself giving a person more than they need because the nearest role was too broad.
Who can invite whom
Inviting is deliberately asymmetric, so an Admin cannot quietly promote someone above themselves.
| Action | Creator | Owner | Admin | Everyone else |
|---|---|---|---|---|
| Invite someone as Owner | Yes | Yes | No | No |
| Invite as Admin or lower | Yes | Yes | Yes | No |
| Promote a member to Owner | Yes | Yes | No | No |
| Remove a non-Owner | Yes | Yes | No | No |
| Remove an Owner | Yes | No | No | No |
That last row is the one worth remembering. Removing an Owner is reserved for the person who created the workspace, see Create your workspace for why the creator is tracked separately.
Handles
Every member gets a handle for @mentions, an avatar and a title. Mentioning someone puts the task in their Inbox.
Shared material gets a home that is not one person’s by living in a project, see Where things live.
Access is checked on our side, always
Roles are not just a matter of which buttons the interface shows you. Every request is re-checked on the server against your membership and role, so hiding a button is a convenience, never the security boundary.
Next
Once people are in, decide where their work should live: Where things live.