> 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/what-is-a-user-role.md).

# What is a User Role?

In XoroERP, every user is assigned a specific role. Each role comes with a set of permissions and privileges assigned in the Access Manager module. These roles define the scope of actions a user can perform within the system. For example, the Admin role grants full access to all modules, whereas the Accounting role provides access solely to accounting-related functions.

### Importance of User Roles

When a new user is added to the system, assigning them a specific role is mandatory. A user role provides the following benefits when navigating the system:

* **Security**: By limiting access based on a role, the system's overall security posture is improved.
* **Efficiency**: Users find what they need faster because they are not sifted through irrelevant content or functionalities.
* **Management**: You can easily manage permissions and access based on a role, rather than handling individual permissions manually.


---

# 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/what-is-a-user-role.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.