> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/1-7-2/documentation/user-management/roles.md).
# Roles
## Overview
This gives a quick overview about the roles and their permissions.
## Creating New Roles
1. Click the + button in the top right toolbar to add a role.
2\. Choose a name for the new role and either copy permissions from an already existing role or add specific permissions. Finish the creation by clicking the `CREATE` button in the bottom right.
## Editing Roles
A role can be edited in regards to its name, adding and removing custom permissions as well as copying permissions from other roles.
1. Open the edit dialog by clicking on one of the rows in the overview.
2. Change the name accordingly and confirm the changes by clicking the `UPDATE` button.
## Deleting Roles
1. Open the edit dialog by clicking on one of the rows in the overview.
2. Delete the Role by clicking the `DELETE` button in the top right of the dialog.
3. Click the delete button in the dialog.
---
# 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.cybus.io/1-7-2/documentation/user-management/roles.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.
