Workspaces partition access, they meter nothing
What a workspace separates, what it does not, and why the current workspace lives in the URL.
Three levels, and it pays to keep them apart from the start.
| Level | What it carries |
|---|---|
| User | A person. One identity, however many organizations |
| Organization | The customer in the commercial sense: plan, seats, volume, billing, SSO |
| Workspace | The drawer: inboxes, soon API keys, and its own member list |
What a workspace does
It partitions access. A member of a workspace sees its inboxes and their messages; they do not see those of a workspace they do not belong to. That is the useful property when two teams share a subscription without wanting to share their test mail.
What a workspace does not do
It meters nothing. Not volume, not seats, not inboxes: those ceilings belong to the organization, and quotas-et-retention explains why. Creating another workspace therefore lifts no limit.
This is written down because it is the natural mistake: in many tools a “project” is also a unit of measurement. Here it is not.
The current workspace is in the URL, never in the session
/w/<slug>/inboxesalways designates the same workspace, whichever tab opens it. Switching workspace is therefore a navigation, not an invisible state change.
The consequence that matters: a link shared in a ticket or a message opens exactly what its author was looking at. An unknown slug gives an explicit dead end rather than a silent redirect to another workspace — landing elsewhere without knowing it means reading the wrong inbox while believing you are reading the right one.
The menu carries the boundary
In the sidebar, a single framed block holds the workspace selector and the entries scoped to it. Below, outside the frame: “ORGANIZATION”, then “ACCOUNT”.
That frame answers a precise defect seen elsewhere: when “Settings” sits at the same level as everything else, nothing says what each setting governs — the account, the team, or the project at hand.
The default workspace
Every organization has one, and it is reachable by all its members. Additional workspaces have their own list. See membres-et-sieges for roles.
Moving an inbox
An inbox can be moved from one workspace to another. Its past usage is not rewritten: it is keyed on the organization, which has not changed. No effect on the bill, since billing is per organization.
Known limits
- No workspace setting is quantitative, and that is intended.
- Only one organization is taken into account by the application today. If you belong to several, the first one is shown; the organization selector is still to be written.