> ## Documentation Index
> Fetch the complete documentation index at: https://to11.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Roles & Permissions

> Control what each member can do with roles, a permission catalog, and session access.

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:

| Role | Typical access |
| - | - |
| `owner` | Full control of the tier, including deleting it. |
| `admin` | Manage configuration and members; read sessions. |
| `developer` | Read and change configuration; read sessions. |
| `viewer` (`member` at the organization tier) | Read-only 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](https://to11.ai/docs/platform/team.md) 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:

| Area | Examples |
| - | - |
| Organization | Create, read, update, delete organizations |
| Workspace | Create, read, update, delete workspaces |
| Project | Read, create, update, and delete projects; manage a project's [environments](https://to11.ai/docs/platform/environments.md) |
| Members & invites | List members, manage members, manage invitations |
| Prompts | Read, create, update, and archive prompts — of [either kind](https://to11.ai/docs/skills/concepts.md). Publishing a version needs `prompt:create` |
| API keys | Create, list, rotate, revoke keys |
| Ingestion | Upload [session](https://to11.ai/docs/sessions/overview.md) transcripts to a project (`ingest:write`) |
| Sessions | Read a project's sessions (`sessions:read`) |
| Audit | Read and export the project audit log and the organization's admin audit log |
| Integrations | See the organization's GitHub and Slack integrations (`integration:read`); connect GitHub and Slack, assign GitHub repositories to projects and refresh them from GitHub, and disconnect Slack (`integration:admin`) |
| Pull requests | List the pull requests of the GitHub repositories assigned to a project (`pull_request:read`); sync one from GitHub (`pull_request:update`) |

The catalog is enforced server-side: every protected action checks for the permission it requires, and [API keys](https://to11.ai/docs/platform/api-keys.md) draw their scopes from the same catalog.

> [!NOTE]
>
> **Skills add no permission of their own.** A [skill](https://to11.ai/docs/skills/concepts.md) 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](https://to11.ai/docs/sessions/overview.md): `sessions:read` to read them, and `ingest:write` to upload them.

| Permission | Scope | Grants |
| - | - | - |
| `sessions:read` | Project | Read every session uploaded to the project. |
| `ingest:write` | Project | Upload session transcripts to the project. |

### Which roles hold them

| Tier | Role | `sessions:read` and `ingest:write` |
| - | - | :-: |
| Organization | `org_owner` / `org_admin` / `org_developer` | Y |
| Organization | `org_member` | |
| Workspace | `workspace_owner` / `workspace_admin` / `workspace_developer` | Y |
| Workspace | `workspace_viewer` | |
| Project | `project_owner` / `project_admin` / `project_developer` | Y |
| Project | `project_viewer` | |

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](https://to11.ai/docs/platform/team.md) 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](https://to11.ai/docs/platform/api-keys.md)) 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

> [card] [Team](https://to11.ai/docs/platform/team.md)
>
> Assign roles to people.

> [card] [API keys](https://to11.ai/docs/platform/api-keys.md)
>
> Scope programmatic access.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.