Skip to main content
Access in to11 is governed by permissions. A permission is a single capability — such as creating an API key or archiving a prompt. Permissions are grouped into roles, and roles are assigned to members.

Roles

A role is a named set of permissions. Assigning a role to a member grants them every permission it contains. Roles exist at three tiers — organization, workspace, and project — and each tier ships the same four built-in roles, from most to least access: A member’s effective access is the union of the roles they hold across the tiers that apply to them — an org_developer who is also a project_admin on one project has admin access there and developer access elsewhere. Assigning roles. Set a person’s organization role when you invite them, and adjust roles — including per-workspace and per-project roles — from the Team page. Changing someone’s role grants every capability the new role carries.

The permission catalog

Permissions are scoped to the level they act on. The catalog spans, among others: The catalog is enforced server-side: every protected action checks for the permission it requires, and API keys draw their scopes from the same catalog.
Skills add no permission of their own. A skill is the second kind of prompt, so it is gated by the prompt permissions above rather than by a parallel set. Two are worth naming because they are not where a reader would look first:
  • Importing a skill from a folder needs prompt:create — the scope that creates versions, which is what an import produces. Its own scope would mean a maintainer who can create versions cannot import one, which is a distinction nobody has asked for.
  • Resolving organization/workspace/project to a project id needs project:read — deliberately narrower than the three calls it replaces, which need organization-level read. Resolution is a lookup, not a way to enumerate: it answers about a project you can already reach, and a project you cannot reach is reported the same way as one that does not exist.

Session access

Two permissions gate a project’s sessions: sessions:read to read them, and ingest:write to upload them.

Which roles hold them

Developer, admin, and owner roles at every tier hold both. Viewer-tier roles and org_member hold neither.

Granting session access

  • To a teammate — on the Team page, open the person’s role popover at the relevant tier and assign a role that carries sessions:read. Changing the role grants every capability the new role carries, not just this one.
  • To an API key — create a key (see API keys) with the sessions:read scope to read sessions, or ingest:write to upload them.
  • To revoke — change the person’s role to one without the permission, or revoke the API key. The change takes effect on the next request.

Next steps

Team

Assign roles to people.

API keys

Scope programmatic access.