> 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

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 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://cortex-docs.paloaltonetworks.com/cortex-xpanse/users-and-roles.md?ask=<question>&goal=<endgoal>
```

`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.