> 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/gateway-guide/roles-management/manage-roles-in-cortex-gateway.md).

# Manage roles in Cortex Gateway

View, create, edit, and delete roles in Cortex Gateway.

[Cortex Gateway](https://cortex-gateway.paloaltonetworks.com/accounts) is a centralized portal for managing tenants, users, roles, and user groups.

{% hint style="info" %}

### Note

You must have an Account Admin role to manage tenants, users, roles, and user groups in Cortex Gateway.
{% endhint %}

When you log into Cortex Gateway you can see the available tenants according to Cortex products, which you can manage according to your CSP account, including activation and licenses.

In the **Permission Management** page, in the **Roles** tab, you can manage roles created in Cortex Gateway or the tenant.

You can view, create, and edit roles and permissions that have been created in Cortex Gateway (**All Tenants**) or a tenant. If you create a new role, it applies to all tenants. For example, you may want a management role to have the same permissions across all tenants. To limit them to a specific tenant, create the role in the tenant.

When right-clicking a role, you can perform several actions, such as editing a role, saving it as a new role, and removing a role (deleting a role that is not assigned to a user).

### **Create a role in the Cortex Gateway**

The roles you create provide more granular access control. You can add as many new roles as you need and combine them with user groups. You can set permission levels for viewing pages, limit potential actions, limit job actions, and limit scripts.

{% hint style="info" %}
You must have an Account Admin role to create or edit a role.

For Cortex XSOAR, you cannot define advanced settings such as managing shifts or setting default dashboards in Cortex Gateway, as these are exclusive to the Cortex XSOAR tenant.

We recommend copying and modifying out-of-the-box roles.
{% endhint %}

1. In Cortex Gateway, go to **Permission Management** → **Roles** → **New Role**.
2. Add the **Role name** and a meaningful **Description**.
3. In the **Components** tab, define the role-based permissions and save the role.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>In Cortex XDR/XSIAM/AgentiX, the <strong>Datasets</strong> tab is disabled in the Cortex Gateway as you can only set dataset access permissions in Cortex XDR/XSIAM <strong>Access Management</strong>.</p><p>For more information, see the following:</p><p>Cortex XSIAM: <a href="/cortex-xsiam/onboard-cortex-xsiam/post-deployment/manage-user-roles-and-access-management/manage-user-roles.md">Manage user roles</a></p><p>Cortex XDR: <a href="/cortex-xdr-3.x/cortex-xdr-3.x-documentation/onboard-and-configure-cortex-xdr/post-deployment-steps/manage-user-roles-and-access-management/manage-user-roles.md">Manage user roles</a></p><p>Cortex AgentiX: <a href="/cortex-agentix/configure-cortex-agentix/users-and-roles-management/roles-management/manage-roles-in-the-cortex-agentix-tenant.md">Manage user roles</a></p></div>
4. You can create user groups and add roles to them (recommended), assign roles directly to users after they have been added, or both.


---

# 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/gateway-guide/roles-management/manage-roles-in-cortex-gateway.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.