> For the complete documentation index, see [llms.txt](https://docs.tomorrowx.com/cap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomorrowx.com/cap/product-reference/administration-functions/managing-user-roles.md).
# Managing User Roles
User roles are used to define the individual access rights of a standard user.
Role
Very fine-grained authorities can be set in a user role, which can then be applied to any number of users.
{% hint style="info" %}
Note: When you create a new server, you must update each role that will have access to that server to include the relevant authorities. If you do not, the role will automatically be excluded from accessing the new server.
{% endhint %}
{% hint style="info" %}
Note: When you create a new repository, you must update each role that will have access to that repository to include the relevant authorities. If you do not, the role will automatically be excluded from accessing the new repository.
{% endhint %}
If you have case managers defined, they will show alongside the ability to manage which tasks and queues can be accessed under which circumstance. Please see “Working with Case Managers” earlier in this manual for more details.
---
# 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://docs.tomorrowx.com/cap/product-reference/administration-functions/managing-user-roles.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.