Partition access with workspaces
A workspace separates who sees which inboxes. It splits neither your volume nor your seats.
Three levels, worth keeping apart from the start.
| Level | What it carries |
|---|---|
| User | A person. One identity, however many organizations |
| Organization | The plan, the seats, the volume, the billing, SSO and the API keys |
| Workspace | The inboxes, and its own member list |
What a workspace separates
It separates who sees what. A member of a workspace sees its inboxes and their messages, and does not see those of a workspace they do not belong to.
That is what you want when two teams share a subscription without sharing their test mail. An API key follows the same boundary: it belongs to the organization, and you choose the workspaces it reaches, see API keys.
What a workspace does not separate
It meters nothing. Not volume, not seats, not inboxes: those ceilings belong to the organization. Creating one more workspace therefore lifts no limit, see Quotas and retention.
This is written here because in many tools a “project” is also a unit of measure. Here, it is not.
Share a link to a workspace
The current workspace is in the URL:
/w/<slug>/inboxes
That address always names the same workspace, whichever tab opens it. A link pasted into a ticket therefore opens exactly what its author was looking at.
An unknown slug gives an explicit error page, never a redirect to another workspace: landing somewhere else without knowing means reading the wrong inbox while believing you are reading the right one.
Find the right setting in the sidebar
One boxed block holds the workspace selector and the entries that are set at workspace level. Below the box come “ORGANIZATION”, then “ACCOUNT”.
The box tells you what each setting sets: the current workspace, the whole team, or your account.
The default workspace
Every organization has one, reachable by all its members. Additional workspaces have their own member list, see Members and seats for the roles.
Move an inbox between workspaces
You can do it at any time, with no effect on your invoice: its past usage stays attached to the organization, which has not changed.
Known limits
- A workspace carries no quantitative setting. Quotas are set per organization and per inbox, not per workspace.
- No workspace role beyond member and administrator, see Members and seats.
Checked on Is this article wrong or incomplete?