> For the complete documentation index, see [llms.txt](https://guides.dojah.io/user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.dojah.io/user-manual/settings/teams/manage-teams-and-permissions.md).
# Manage Teams and Permissions
The Roles and Permissions page in Dojah allows you to create and manage different roles for your users, as well as the permissions associated with each role. This allows you to grant or deny users access to specific features and functionality on the Dojah platform.
To use the Roles and Permissions page, follow these steps:
1. Go to the **Settings** section of the dashboard.
2. Click the **Teams** tab.
3. Also click the **Manage Teams & Permissions** Button
4. You will see a list of all existing roles. To create a new role, click the **New Role** button.
5. Enter a name for the new role and select the permissions you want to associate with it.
6. Once you have finished configuring the new role, click the **Save changes** button
You can also edit or delete existing roles by changing the **Configurations** set or **Delete Role** buttons
---
# 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://guides.dojah.io/user-manual/settings/teams/manage-teams-and-permissions.md?ask=&goal=
```
`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.