> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/user/user-role/user-role-centre.md).

# User Role Centre

The User Role Centre houses all the roles created within the system. It provides you with a comprehensive overview of the various roles established to manage user access and permissions. Within the centre, you can create and modify roles, thereby shaping the access control framework according to organizational requirements.

### Key Features

* **Comprehensive Role Overview**: View all user roles in one centralized location.
* **Role Management**: Easily create, modify, and delete roles to align with organization's evolving needs.
* **Permission Assignment**: Assign specific permissions to each role, ensuring users have appropriate access levels.
* **Scalability**: Scale your role management process as your organization grows, without losing control or oversight.

### Use Cases

* **Access Control Implementation**: Define and enforce access control policies by creating roles with specific permission sets.
* **Compliance and Audit**: Maintain a clear and auditable trail of role assignments and modifications to comply with internal and external audit requirements.
* **Security Management**: Minimize security risks by ensuring users only have access to the information and functionality necessary for their roles.


---

# 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.xorosoft.com/xoroerp-1/admin/user/user-role/user-role-centre.md?ask=<question>&goal=<user_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.
