> 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-xsiam/reference-and-developer-docs/role-based-access-control/configuration-permissions/integrations-permissions.md).
# Integrations Permissions
Manage access to Cortex XSIAM integration configuration and available instances.
Controls access to the Integration Permissions page, a command-level access control layer that determines which roles are allowed to execute specific integration commands. This is distinct from the Integrations permission, which controls access to integration instances and their configuration.
Integrations Permissions provides fine-grained, per-command role restrictions on top of the broader integration access model. Access the Integration Permissions page by going to Settings → Configurations → Data Collection → Integration Permissions.
| Permission | Description | Role Example |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None | Users cannot access the Integration Permissions page and have no visibility into command-level role restrictions. | |
| View | The user can view the hierarchical table of integrations, instances, and commands along with their assigned role restrictions on the Integration Permissions page, but cannot edit, modify, or use batch edit. | SOC 1, 2, and 3 Analysts, and Threat Hunters: Modifying command permissions is an administrative function. |
| View/Edit | Read and Write permission on the Integration Permissions page, including edit, assign, or remove roles from commands, use batch edit, and save changes. | Security Engineer: Responsible for configuring and maintaining integration command permissions. Needs to assign roles to commands, use batch edit for bulk changes, and manage the command-level access control model. |
**Required and recommended permissions**
To access the Integration Permissions page, the following permissions are required/recommended:
| Permission | Permission Level | Reason |
| ------------ | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Integrations | View | - View: Having the Integrations View ensures the parent navigation section is accessible and provides context for the integration instances whose commands are being restricted. Strongly recommended.
- View/Edit: Users who manage command-level permissions typically also need to configure integration instances. Recommended.
|
| Credentials | View | Provides context about credential sets used by the integrations whose commands are being managed. No direct dependency, but useful for holistic integration management. |
---
# 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-xsiam/reference-and-developer-docs/role-based-access-control/configuration-permissions/integrations-permissions.md?ask=&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.