> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/organization-and-account-settings/users-and-roles/create-new-role.md).
# Create new role
{% hint style="success" %}
**Access Type**: Admin
{% endhint %}
A role is a customizable collection of permissions that dictate what kind of access a user has across Didomi product and features. In this article, we will cover how to create a new role in your organization's account so that it can be assigned to other users.
Click **My Organization** and select **Users & Roles** from the drop-down menu.
Select the **Roles** tab and click the **Create a role +** button.
On the subsequent page, give the new role a name and an optional description.
Next, navigate to the feature cards and use the provided drop-down menu to select the role's access type for that feature. Possible access types include:
* No Access
* Viewer
* Editor
{% hint style="info" %}
Every Didomi account comes pre-populated with an non-editable Admin role. [Click here](/organization-and-account-settings/users-and-roles/access-type-overview.md) for more information on the Admin role and/or the access types assignable to a role.
{% endhint %}
Click **Save & Close** when finished.
The new role is created and can be assigned to users in your organization's account.
---
# 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.didomi.io/organization-and-account-settings/users-and-roles/create-new-role.md?ask=&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.
