Account & teams

Organisations

An organisation sits above workspaces. It's where larger teams manage membership and billing in one place while keeping each workspace's collections separately scoped.

Last updated 2026-05-29

Where organisations fit

The hierarchy is organisation → workspace → collection. An organisation bundles several workspaces under shared administration and a single billing relationship, without merging their contents — each workspace keeps its own collections and member list.

A key rule: org membership and workspace membership are separate. Belonging to the organisation does not automatically grant access to any workspace’s private collections — workspace access still follows workspace roles (see Workspaces). This keeps “who can administer the org” distinct from “who can open this collection”.

Organisation settings

Open Organisation settings (under /orgs/…) to find:

  • General — the organisation name, created date, ID, and state.
  • Members — list members and their roles (owner / admin / member); invite or remove members if you’re an admin.
  • Plan & billing — view the current plan tier and open the billing portal to manage payment.
  • Workspaces — every workspace under the organisation.

Roles

Organisation roles (owner / admin / member) govern administration of the org itself — membership, billing, and which workspaces it contains. They are mapped independently of workspace roles, so an org admin isn’t automatically an admin (or even a member) of every workspace beneath it.

Invites

Admins invite members by email; accepting the link joins them to the organisation. An invite can also carry workspace grants so a new member lands with the right workspace access from the start.

See also