Core concepts
One workspace per customer.
Every project, member, invoice and key belongs to a workspace, and the API checks that boundary on every request.
The boundary
Every workspace route carries the workspace in its path. The API first checks that the caller is a member of it, and answers 404 when they are not, so a workspace nobody shared with you does not even appear to exist. It then checks the role's permission for the action, and answers 403 when it is missing.
Members and invitations
Owners and admins invite people by email with a role. An invitation is valid for seven days and can be resent or revoked. Pending invitations do not take a seat; the seat count is checked again when an invitation is accepted, so two people can never take the last seat.
Switching workspaces
A person can belong to several workspaces. Choosing another one in the dashboard reloads its data from the API, and nothing from the previous workspace stays on screen.
Usage and limits
Each workspace counts its members, API requests and storage against its plan. The overview shows how much is used, and the billing page shows the limits of every plan.