> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/start-here/org-settings/roles-and-capabilities.md).

# Roles and Capabilities

See what every role can do across the tenant, and create, edit, or delete custom roles.

Roles and Capabilities shows every role in your tenant next to the capabilities it grants. An **Organisation Admin** also creates custom roles here, and edits or deletes them.

| Topic        | Details                                                                                                                          |
| ------------ | -------------------------------------------------------------------------------------------------------------------------------- |
| Access       | Roles with **Manage organization roles**. Only **Organisation Admin** carries it.                                                |
| Open it      | Select your avatar, select **Org Settings**, then select **Roles and Capabilities** in the sidebar.                              |
| Scope        | Managing roles is a tenant-level capability. See [Roles](https://docs.uptiq.ai/ai-workbench-qore/control-center/admin/roles.md). |
| Main actions | **Refresh**, **Manage Custom Roles**, and **Create Role**.                                                                       |

Account administrators see the same capabilities table, without the actions to create or manage roles, at **Control Center → Admin → Roles**. See [Roles](https://docs.uptiq.ai/ai-workbench-qore/control-center/admin/roles.md) for what each standard role is for and the capability-by-role tables.

## Read the capabilities table

The page subtitle reads *"Define roles, assign capabilities, and safeguard critical actions."*

**Search** and the **Role type** pill narrow the table. **Role type** offers **All roles**, **System roles**, and **Custom roles**.

The **Capabilities** table has one column for each role. Custom roles carry a **Custom** badge in the column header. Each row is a group of capabilities, such as **Apps**, **Agents**, **Cost control**, **Govern › Publishing Approvals**, **Admin**, or **Settings**. Each cell shows how many of the group's capabilities the role holds, for example *11/11* for a role that holds every **Apps** capability, or *1/11* for a role that holds one of the eleven.

The **Settings** group holds the tenant-level capabilities **Create an account**, **Manage organization brand**, and **Manage organization roles**. **Organisation Admin** holds all nine capabilities in the group, and **Account Admin** holds six.

## Create a custom role

1. Select **Create Role**. The **Create New Role** dialog opens.
2. Enter a name in the **Role** field.
3. To base the role on an existing one, select **Select a role** under **Start from an existing role** and choose a role. The list holds every standard role and every custom role. Choosing a role selects its capabilities, for example *13 selected* for **Viewer**, and you can change the selection.
4. Under **Capabilities**, open each group and use the checkboxes to select the capabilities the role needs. **Search capabilities...** finds a capability by name. The counter beside **Capabilities** shows how many you have selected, for example *0 selected*.
5. Select **Create Role**. Select **Cancel** to close the dialog without saving.

The capability groups are the same ones the table shows: **Apps**, **Agents**, **Knowledge Content**, **Flows**, **Store**, **Integrations**, **Design System**, **Observe**, **Cost control**, **Evals**, **Govern › Agent Controls**, **Govern › Publishing Approvals**, **Govern › Govern Graph**, **Govern › Connectors**, **AI Gateway**, **Admin**, **Settings**, and **Other**. Each group shows how many of its capabilities you have selected out of the total, for example *0/11* for **Apps**.

{% hint style="info" %}
**Give the least privilege that works.** Start from the standard role closest to the job, then remove what the person doesn't need. A person who holds several roles in an account gets all their capabilities added together.
{% endhint %}

## Manage custom roles

Select **Manage Custom Roles**. The dialog reads *"Edit or delete the custom roles defined for your organization."*

It lists each custom role with its **Role** name and a preview of its **Capabilities**, such as *View App* and *Trigger agent*, followed by a count of the rest, for example *+33*. Use **Search** to find a role. Open a row's **Actions** menu to select **Edit** or **Delete**.

Standard roles are not listed here. They appear in the capabilities table with no **Custom** badge.

## Related

<table data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td>Roles</td><td>Choose a standard role and read every capability by role.</td><td><a href="https://docs.uptiq.ai/ai-workbench-qore/control-center/admin/roles.md">Roles</a></td></tr><tr><td>Users</td><td>Invite people and assign them roles in an account.</td><td><a href="https://docs.uptiq.ai/ai-workbench-qore/control-center/admin/users.md">Users</a></td></tr><tr><td>Org Settings</td><td>See which Org Settings pages your role opens.</td><td><a href="https://docs.uptiq.ai/ai-workbench-qore/start-here/org-settings.md">Org Settings</a></td></tr></tbody></table>


---

# 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.uptiq.ai/ai-workbench-qore/start-here/org-settings/roles-and-capabilities.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.
