> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/administer/manage-users-and-access/set-permissions-and-roles-rbac/see-available-roles.md).

# See available roles

{% hint style="info" %}
**Feature availability**

* The Project Editor role is available on Pro Cloud and Self-hosted Enterprise plans.
* The Project Viewer role is only available on Self-hosted Enterprise and Cloud Enterprise plans.
  {% endhint %}

Within projects, there are three user roles: Admin, Editor, and Viewer. These roles control what the user can do in a project. A user can have different roles within different projects.

## Project Admin <a href="#project-admin" id="project-admin"></a>

A Project Admin role has the highest level of permissions. Project admins can:

* Manage project settings: Change name, delete project.
* Manage project members: Invite members and remove members, change members' roles.
* View, create, update, and delete any workflows, credentials, or executions within a project.

## Project Editor <a href="#project-editor" id="project-editor"></a>

A Project Editor can view, create, update, and delete any workflows, credentials, or executions within a project.

## Project Viewer <a href="#project-viewer" id="project-viewer"></a>

A Project Viewer is effectively a `read-only` role with access to all workflows, credentials, and executions within a project.

Viewers aren't able to manually execute any workflows that exist in a project.

{% hint style="info" %}
**Role types and account types**

Role types and [account types](/administer/manage-users-and-access/understand-account-types.md) are different things. Every account has one type. The account can have different role types for different [projects](/administer/manage-users-and-access/set-permissions-and-roles-rbac/organize-work-in-projects.md).
{% endhint %}

| Permission                          | Admin | Editor | Viewer |
| ----------------------------------- | ----- | ------ | ------ |
| View workflows in the project       | ✅     | ✅      | ✅      |
| View credentials in the project     | ✅     | ✅      | ✅      |
| View executions                     | ✅     | ✅      | ✅      |
| Edit credentials and workflows      | ✅     | ✅      | ❌      |
| Add workflows and credentials       | ✅     | ✅      | ❌      |
| Execute workflows                   | ✅     | ✅      | ❌      |
| Manage members                      | ✅     | ❌      | ❌      |
| Modify the project                  | ✅     | ❌      | ❌      |
| Use external secrets in credentials | ✅\*   | ✅\*    | ❌      |
| Manage project secret vaults        | ✅\*   | ❌      | ❌      |

\* Requires **Enable external secrets for project roles** to be enabled by an instance owner or admin. Refer to [Access for project roles](/administer/manage-credentials/use-external-secret-stores.md#access-for-project-roles). This is available from n8n version `2.13.0`.

[Variables](/build/code-in-n8n/define-custom-variables.md) and [tags](/build/manage-workflows/tag-workflows.md) aren't affected by RBAC: they're global across the n8n instance.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.n8n.io/administer/manage-users-and-access/set-permissions-and-roles-rbac/see-available-roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.