People & workspaces
Organisations, workspaces and roles
How access is structured, and what each role can do.
The shape
An organisation is the account — the thing that is billed, and the boundary nothing crosses. Inside it are workspaces: teams, departments, campuses, properties. Experiences live in a workspace.
The roles
Each is cumulative — every role can do everything the one below it can.
| Role | Can |
|---|---|
| Free | Build and publish their own experiences |
| Individual | The above, plus the asset library and themes |
| Workspace Member | Work on the shared experiences in their workspace |
| Workspace Leader | Manage their workspace's members, learners and settings |
| Organisation Admin | Manage every workspace, billing, integrations and org settings |
Someone can be a leader in one workspace and a member in another. Their access is worked out per workspace, not once for the account.
- FreeBuilds and publishes their own experiences.
- IndividualThe above, plus the asset library and themes.
- Workspace MemberWorks on the shared experiences in their workspace.
- Workspace LeaderRuns a workspace: its members, learners and settings.
- Organisation AdminRuns the organisation: every workspace, billing, integrations, settings.
Learners are not a role
Learners are a different kind of membership, not a rung on this ladder. A learner does not get "less than a member" — they get a different surface entirely. Promoting a learner to a member is a deliberate change, not an increment.
That is why a learner never appears on Members, and why nobody on Students has a role beside their name. See The learner roster.
What you cannot reach, you cannot see
An experience in a workspace you have no access to does not appear as a locked row. It is not there at all. That is intentional: telling you something exists is itself information.