Inviting somebody, and what a seat means
Three ways to add a member, three roles, and how seats are counted.
The three roles
| Role | What they can do |
|---|---|
| Owner | Everything, including the shape of the organization and its deletion |
| Admin | Manage inboxes, members, workspaces, SSO |
| Member | Use it: read the inboxes of the workspaces they belong to |
A plain member sees the organization form read-only, and the danger zone appears to owners alone.
Three ways to add somebody
By email. The invitation is sent to the address you give. The normal path when you know who you are inviting.
By personal link. The same invitation, but you get the link and pass it on yourself — useful when the mail does not arrive, or when the person prefers another channel.
By organization link. A short-lived shareable link, with its role, its validity, a number of uses and a revoke button. This is what you want to onboard three people the same morning without typing three addresses.
All three live in Settings › Members.
The join pages are public, deliberately
/join/<token> and /invitations/<id> open without an account. They have to: a
shared link is by definition opened before sign-up, and the screen must be able to
tell the guest who is inviting them before they create an account.
Seats
A seat is a member of the organization. The ceiling belongs to the plan, and it is counted for the organization, not per workspace: adding somebody to a second workspace does not consume a second seat.
When the ceiling is reached, the invitation is refused and names the plan required, rather than being accepted and then silently ineffective.
Revoking
Removing a member cuts their access. A session already open may however keep answering for up to five minutes: the session cookie carries its own signed copy, and deleting a row in the database does not reach a cookie already sitting in a browser.
This is written here because it is exactly the kind of delay worth knowing before you need it. If the departure is sensitive, also change what the person could reach — see compte-et-securite.
Known limits
- No workspace role beyond member and admin.
- No banning. Access revocation is real; a ban that was not enforced at sign-in would be a security feature in name only.