> 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/duplicate-a-role.md).
# Duplicate a 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 duplicate a role in your organization's account.
{% hint style="info" %}
Duplicating a role can streamline the process to create a new role, especially if there are only minor differences between the original role and the duplicated role.
{% endhint %}
Click **My Organization** and select **Users & Roles** from the drop-down menu.
Select the **Roles** tab and navigate to a role on the list. Click the **Duplicate** icon inline with the role name.
Use the subsequent screen to give your duplicated role a name. By default, Didomi will append *copy* to the original name of the role unless otherwise edited. Click **Create role** when finished.
The duplicated role will be created. If necessary, click the **Edit** inline with the duplicated role to edit the description and access types for the role.
---
# 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/duplicate-a-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.
