> 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/roles-and-permissions-setup.md).

# Set up roles and permissions

Assign built-in roles (Owner, Admin, Developer, Operator, Viewer, End User), create custom roles, and manage team access.

### The 6 built-in roles

fastn has 6 built-in roles. View them under **Settings → Roles** (Owners and Admins):

| Role          | Permissions | Description                                                                           |
| ------------- | ----------- | ------------------------------------------------------------------------------------- |
| **Owner**     | 44          | Can manage admins and transfer ownership.                                             |
| **Admin**     | 44          | Full access within the organization and its 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, widgets, events and the Unified API. |
| **End User**  | 35          | Uses the embed widget: creates connections, runs agents.                              |

Each built-in role carries a **Built in** badge. Selecting one shows its permission matrix and the count it holds out of 44.

### Permission categories

Permissions are grouped into 11 resources, 44 in all:

| Resource            | Available actions                                               |
| ------------------- | --------------------------------------------------------------- |
| **Connectors** (5)  | create, read, update, delete, write                             |
| **Connections** (6) | create, read, update, delete, share, decrypt                    |
| **Workflows** (7)   | create, read, update, delete, execute, deploy test, deploy prod |
| **Users** (5)       | create, read, update, invite, remove                            |
| **Settings** (3)    | read, update, manage                                            |
| **Events** (5)      | create, read, update, delete, replay                            |
| **Secrets** (3)     | read, write, delete                                             |
| **Executions** (2)  | create, read                                                    |
| **Widgets** (4)     | create, read, update, delete                                    |
| **Customers** (1)   | create                                                          |
| **Unified API** (3) | read, execute, customize                                        |

Agents and tools are no longer grantable permissions. Using the AI assistant and reading the audit log are gated by role instead, and the Roles screen names them separately.

#### What each role gets

**Owner / Admin** - All 44 permissions. Full access to everything.

**Developer** - 36 permissions: every Connectors, Connections, Workflows (including deploy prod), Events, Secrets, Widgets and Unified API permission, plus read on Users and Settings, and create on Customers. Cannot manage people, change settings or read the audit log.

**Operator** - 21 permissions. Can create, read and update connectors, manage connections, run workflows and deploy them to test, manage widgets, and read, update and replay events. Cannot create new workflows or deploy to production, and has no Secrets permissions.

**Viewer** - 6 permissions. Read-only on connectors, connections, workflows, widgets, events and the Unified API. Cannot read executions, users, settings or secrets, and cannot run anything.

**End User** - 35 permissions. Customer-facing access through the widget. Can create and manage connections, author and run workflows, and manage users and settings inside their own customer.

### Assigning roles

1. Go to **Settings → People**.
2. Find the team member in the table.
3. Click **Change role** on their row.
4. Pick the new role.

The People table shows: **Person**, **Role**, **Status**, **Added**, **Access** (time-limited access, if any).

Filter by role with the chips above the table, or by status with the dropdown. To change several people at once, tick their rows and use **Change role…** in the bar that appears.

**Change role** is disabled on Owner rows (an owner's role moves through **Transfer Ownership**) and on your own row.

### Creating custom roles

If the built-in roles don't fit your needs, create a custom role:

1. Go to **Settings → Roles**.
2. Click **Custom role**.
3. Pick the built-in role it is **Based on**, name it, and untick the permissions it should not have.
4. Save.

Alternatively, duplicate an existing role and modify it:

1. Click on a role (e.g., Developer).
2. Click **Duplicate**.
3. Adjust the permissions as needed.
4. Save.

A custom role can only narrow its base role: ticking a permission the base role does not hold grants nothing. Assign a custom role to a person on the People screen, or to a customer tier under Settings → Billing.

### Audit trail

Actions across the organization are logged:

1. Go to **Settings → Audit log** (Owners and Admins).
2. Filter by: **All people**, **All actions**, **All types**, and a date range.
3. Columns: **Who, Action, Resource, Customer, Result, When**.
4. Actions include: `auth.login`, `workflow.execute`, `connection.update`, and others.
5. Results: **Success**, **Failed**, or **Not recorded**.

### What you've learned

* The 6 built-in roles and their permission counts
* The 11 resources permissions are grouped into
* How to assign roles to team members
* How to create custom roles or duplicate existing ones
* Audit log for tracking actions


---

# 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/roles-and-permissions-setup.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.
