> 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-agentix/onboard-cortex-agentix/post-deployment-steps/set-up-users-and-roles.md).

# Set up users, groups, and roles

Set up Cortex AgentiX and Cortex Gateway users, user groups, roles, role-based access control (RBAC), and SAML SSO authentication.

Set up users, user groups, roles, and authentication in Cortex AgentiX and Cortex Gateway. Cortex uses role-based access control (RBAC) to grant each user the minimum permissions required.

### Create user roles

Roles enable you to define permissions for specific components, such as issue data, playbooks, scripts, and jobs. For example, you can create a role that allows users to edit the properties of issues, but not delete issues. You can create new roles or customize out-of-the-box roles.

If you assign one or more roles to an issue, only users with those roles can view and interact with the issue. For example, you might have an issue with sensitive data that should only be accessible to Tier-1 analysts and managers.

Roles can also be used to define permissions for integration commands. On the Integration Permissions page, you can assign roles to specific integration instances (all commands for that instance) or specific integration instance commands. For example, you could assign the Generic Export Indicators Service integration instance the Account Admin role, or you could restrict certain commands in the Core Rest API to a specific role. For more information, see Integration Permissions.

For more information about out-of-the-box roles, permissions, and how to create roles, see [Roles management](/cortex-agentix/configure-cortex-agentix/users-and-roles-management/roles-management.md).

### Create user groups

While roles can be assigned directly to users, we recommend creating user groups. Each user group has a single role associated with it, but each user group can contain multiple users, and user groups can be nested within each other, enabling you to further refine your RBAC requirements. Users can belong to several user groups.

For more information about user groups and how to create them, see [User group management](/cortex-agentix/configure-cortex-agentix/users-and-roles-management/user-group-management.md).

After adding users, assign those users to user groups or assign a direct role.

### Set up user authentication

You can create users in the Customer Support Portal or by using SAML Single Sign-On (SSO) in the tenant. After you create users, they authenticate by doing the following:

* Authenticate through the Customer Support Portal
* Authenticate by using SAML Single Sign-On (SSO) in the Cortex tenant

For more information about setting up authentication, see [Set up authentication](/cortex-agentix/configure-cortex-agentix/users-and-roles-management/set-up-authentication.md).

### Manage users

By default, users do not have roles assigned and do not automatically have access to tenant data until you assign them a role or add them as members of a user group that has an assigned role.

For more information about how to manage users, see [User management](/cortex-agentix/configure-cortex-agentix/users-and-roles-management/user-management.md).


---

# 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-agentix/onboard-cortex-agentix/post-deployment-steps/set-up-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.