> For the complete documentation index, see [llms.txt](https://docs.finout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finout.io/settings/role-based-access-control-rbac/managing-roles.md).

# Managing Roles

The Roles page contains all of your default or custom roles. In Finout, you have two types of roles:

* **Default roles** are out-of-the-box roles provided by Finout, see the [roles and permission overview](/settings/role-based-access-control-rbac/role-permissions.md) for all default roles and their permissions. Here you can add custom roles or manage your existing roles.
* **Custom roles** are created by selecting [permissions ](/settings/role-based-access-control-rbac/managing-roles/permissions-list.md)that make up the role. A permission specifies which actions a user can perform in Finout. This enables you to assign specific roles to users tailored to your company's needs.

{% hint style="info" %}
**Note**: Access to the roles page is restricted to admins and users with the "Read Roles" permission.
{% endhint %}

<figure><img src="https://downloads.intercomcdn.eu/i/o/17943940/3c703dadc1296d1ac9622b56/image.png?expires=1727770500&#x26;signature=3a950a03d173ec64500e8d2f610d5e7a5453df5567a70463f6d69fec4c1b62d6&#x26;req=0dJmwVvzqDdk2hL085ZhoSHbuljZNYGUb2Kr%2FA8St%2FadJq3cwVUSUJEgq7uA%0AGIzLk5Cl2tz3mDoJ%0A" alt=""><figcaption></figcaption></figure>

1. Find a particular word or phrase by searching all the data on the Roles page
2. A specific role with its permissions. You can click on a role to do [various actions.](/settings/role-based-access-control-rbac/managing-roles/managing-a-role-and-its-permissions.md)
3. [Create a new custom role](/settings/role-based-access-control-rbac/managing-roles/creating-a-custom-role.md).


---

# 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.finout.io/settings/role-based-access-control-rbac/managing-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.