> 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/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/users-and-roles/integration-permissions.md).

# Integration Permissions

Configure integration command permissions with role-based access control in Cortex XSOAR 6.14.

You can use Role Based Access Control (RBAC) to assign commands at the integration instance level. If you have multiple instances of the same integration, you can assign different roles (permission levels) for the same command in each instance.

{% hint style="info" %}

### Note

To restrict access to integrations using RBAC, see [Roles in Cortex XSOAR](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/users-and-roles/roles-in-cortex-xsoar.md).
{% endhint %}

If you want to view or edit integration permissions, go to Settings → INTEGRATIONS → **Integration Permissions**. You can see a list of all the enabled integrations in Cortex XSOAR. Under each integration you can see the following:

* **Commands**: a list of all commands for the integration.
* **Instance**: a list of all instances for the integration.
* **Permitted roles**: a dropdown list of roles you can assign to the command.

Users that do not have command permissions cannot do the following:

* Run the command from the CLI **`(!)`**.
* Complete pending tasks in a Work Plan that run the command.
* Edit arguments for playbook tasks that have this command.
* Select the command when editing a playbook.
* Select a script if using a reputation command.


---

# 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/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/users-and-roles/integration-permissions.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.