> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/settings/manage/roles.md).

# Roles

What each role can do, and how to narrow one.

**Settings → Roles**

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-eaa074891b10b291929b51b8fe018bac20fa2371%2Fsettings-roles.jpg?alt=media" alt="The Roles screen with the built-in roles down the left, Admin selected with every permission held, and its Connectors, Connections and Workflows groups fully ticked"><figcaption><p>Some capabilities are called out as role-gated rather than grantable, such as using the AI assistant and reading the audit log.</p></figcaption></figure>

> What each role can do. A custom role narrows a built-in one; assign either to a person on the People screen, or to a customer tier under Billing.

### The six built-in roles

| Role          | Permissions | Summary                                                                                                                  |
| ------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Owner**     | 44          | Can manage admins and transfer ownership.                                                                                |
| **Admin**     | 44          | Full access within their organization and customers.                                                                     |
| **Developer** | 36          | Builds and deploys connectors, workflows and agents.                                                                     |
| **Operator**  | 21          | Configures connections and runs workflows. Deploys to test only.                                                         |
| **Viewer**    | 6           | Read-only on connectors, connections, workflows, agents, widgets and events. Not executions, users, settings or secrets. |
| **End User**  | 35          | Uses the embed widget: creates connections, runs agents.                                                                 |

Selecting a role on the left shows its permission matrix, the count it holds out of 44, and a percentage bar. Built-in roles carry a **Built in** badge.

### Platform Admin

A seventh role, **Platform Admin**, is platform-level: held by fastn, not something you assign to someone inside your own organization. It does not appear on this screen.

### Roles here are not API-key permissions

The six roles on this screen govern **people**. API keys carry their own permission presets (**Admin**, **Developer**, **Operator**, **Viewer** (the default), **End User**, **Embed backend** and **Custom**), chosen on the key creation dialog. The names overlap, but they are two separate systems configured in two different places; granting a person the Developer role does nothing to a key, and vice versa. See [API keys](https://docs.fastn.ai/embed/api-keys.md).

### The permission matrix

Eleven resources, 44 permissions in all:

| Resource        | Permissions                                                     |
| --------------- | --------------------------------------------------------------- |
| **Connectors**  | create, read, update, delete, write                             |
| **Connections** | create, read, update, delete, share, decrypt                    |
| **Workflows**   | create, read, update, delete, execute, deploy test, deploy prod |
| **Users**       | create, read, update, invite, remove                            |
| **Settings**    | read, update, manage                                            |
| **Events**      | create, read, update, delete, replay                            |
| **Secrets**     | read, write, delete                                             |
| **Executions**  | create, read                                                    |
| **Widgets**     | create, read, update, delete                                    |
| **Customers**   | create                                                          |
| **Unified API** | read, execute, customize                                        |

### Capabilities that are not permissions

Some things are gated by role directly rather than by a grantable permission, and cannot be turned on or off per user:

* **Use the AI assistant**: the agent service checks the caller's role. Every built-in role except Viewer has it.
* **Read the audit log**: `/api/v1/audit-log` is restricted to account owners and admins.
* **Manage the Unified API catalog**: Platform Admin only. Admin and Owner can read and execute the catalog but not change it.

### Custom roles

**Custom role**, or **Duplicate** on a built-in, creates a role that *narrows* its parent. You pick the built-in it is **Based on**, then take permissions away; you cannot add ones the parent does not have.

Assign a custom role to a person on [People](https://docs.fastn.ai/settings/manage/people.md), or to a customer tier under [Billing](https://docs.fastn.ai/settings/manage/billing.md), which is how you scope what the people at your customer may do in the embed.

### The boundary worth knowing

**Operator** deploys **to test only**: it holds `deploy test` on Workflows but not `deploy prod`. **Developer** holds every Workflows permission, `deploy prod` included, so it is the role that can push to production.

`decrypt` on Connections and `read` on Secrets are the two most sensitive permissions in the matrix. Viewer holds neither. Operator holds every Connections permission, `decrypt` included, but no Secrets permission.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fastn.ai/settings/manage/roles.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
