> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xpanse/users-and-roles.md).

# Users and roles

Learn how to configure and manage Cortex Xpanse users, roles, and user groups. Assign roles and set up authentication for users.

Cortex Xpanse uses role-based access control (RBAC) to manage user roles with specific permissions for controlling user access. RBAC helps manage access to Cortex Xpanse components, so that users, based on their roles, are granted minimal access required to accomplish their tasks.

You can update users and roles by going to **Settings** → **Configurations** → **Access Management**. In the **Access Management** section, you can do the following:

* Manage users, such as deactivating users, add user roles, import multiple user roles, and view user details such as name, email address, last log in, and user type.
* Manage user groups, which includes creating new user groups and modifying existing ones.
* Manage roles and access permissions on the Roles page. You can add as many roles as required and change their permission levels.
* Configure scope-based access control (SBAC) for users and user groups.
* Set up user authentication.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xpanse/users-and-roles.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.