> For the complete documentation index, see [llms.txt](https://resmocom.gitbook.io/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resmocom.gitbook.io/product/users-and-permissions/rbac-role-based-access-control.md).

# RBAC (Role-Based Access Control)

**Role-Based Access Control** restricts access to specific resources based on a person's defined role within an organization. Through RBAC, you can control what each role can do at a granular or broad level. Individuals can only access and see information, such as integrations or resources necessary to perform their job.  

**The RBAC management** feature provides policies and roles to manage access controls. Policies are access/deny statements that can be attached to roles to define their permissions. This ensures that an individual is granted only necessary permissions and can't access sensitive data beyond their access level or perform higher-level tasks.

{% hint style="info" %}
There are two types of [roles on Resmo](https://docs.resmo.com/product/users-and-permissions/rbac-role-based-access/custom-roles-and-policies#roles).

* **Managed roles:** Created by default and managed by Resmo. They cannot be edited or deleted.
* **Custom roles:** Can be created, edited, and deleted by users.

Also, [see available user roles](/product/users-and-permissions/user-roles.md).
{% endhint %}

### [Roles](https://docs.resmo.com/product/users-and-permissions/rbac-role-based-access/custom-roles-and-policies#roles)

* Users can list all roles from Settings>Roles and see details of each. Custom roles can be created, edited, and deleted. [See how to create a custom role](https://docs.resmo.com/product/users-and-permissions/rbac-role-based-access/custom-roles-and-policies#how-to-create-a-custom-role).
  * A role can have a maximum of 10 policies.
  * Existing users in an account can be updated with existing roles. 
  * A user can invite users with existing Roles from the User Invitation page. By default, an invited user has UserRole.

### [Policies](https://docs.resmo.com/product/users-and-permissions/rbac-role-based-access/custom-roles-and-policies#policies)

* Policies can be listed from Settings>Policies. Each policy can be seen in detail, while custom policies can also be edited. Policies comprise role a name, description, and statement. [See how to create a custom policy](https://docs.resmo.com/product/users-and-permissions/rbac-role-based-access/custom-roles-and-policies#how-to-create-a-custom-policy).
* [Statements](https://docs.resmo.com/product/users-and-permissions/rbac-role-based-access/custom-roles-and-policies#statements) comprise effect, service, action, and type.
  * Users can leverage the UI dropdown to manage statements or activate the Advanced Mode to use JSON mode when creating a policy.
  * Changes made through the UI dropdown can be seen in JSON mode or vice versa.
  * A user can create a maximum of 10 statements inside a policy.


---

# 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://resmocom.gitbook.io/product/users-and-permissions/rbac-role-based-access-control.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.