Organisations
An organisation owns workspaces on behalf of a team, with its own members. Organisations may not be available on your platform yet.
Organisation roles
Section titled “Organisation roles”| Role | Can |
|---|---|
| Owner | Full control. Can open any of the organisation’s workspaces as owner; every use is recorded and the workspace’s owner is told. |
| Admin | Manage members and workspaces, but can’t open a workspace’s data without being added to it. |
| Member | Gets the organisation’s default access, and can create workspaces if limits allow. |
| Guest | Sees only the workspaces they were given. |
The default role for members is one of: No access, Viewer, Viewer + logs, Developer, Editor.
Settings
Section titled “Settings”- Workspace limits: how many workspaces a member may create, and how large (apps, memory, CPU, storage).
- Agent access: whether API tokens (the CLI and AI agents) can read the organisation’s workspaces. On by default.
- Agent deploy: whether an agent holding the deploy permission may apply a plan it showed. On by default. Workspaces that require approval still wait for a person.
- Audit: owners and admins see the organisation’s activity, filtered by members, workspaces, invitations and transfers.
- Transfer, Leave and Delete (only when it has no workspaces and no other members).
Moving a workspace between accounts redeploys and restarts nothing.