> 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/configure-cortex-agentix/users-and-roles-management/roles-management/role-permissions-by-component/configuration-permissions/integrations-instance-permissions.md).

# Integrations - instance permissions

Controls access to data collection integration instances, such as automation and feed integrations that collect and process data on the **Data Sources & Integrations** page (**Settings** → **Data Sources & Integrations**). It also controls access to classifiers and mappers **Settings** → **Configurations** → **Object Setup** → **Issues** → **Classification & Mapping**.

Data Sources & Integrations page

The **Data Sources & Integrations** page is a unified interface. Access levels are determined as follows:

* Data Sources permission only: Users can view the page and manage cloud accounts (CSP).
* Integrations permission only: Users can view the page and manage data collection integration instances, specifically automation and feed integrations.
* Both permissions: Users have full visibility and can manage both data sources and integrations on the same page.

{% hint style="info" %}

### Note

There are two integration permissions:

* Integrations (under Data Collection): Configure data collection integrations
* Integration Permissions (under Integrations): Configure command permission for integrations.
  {% endhint %}

| Permission | Description                                                                                                                                                                                                                                                                                                                                                                                                                                      | Roles Example                                                                                                                                                                                            |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None       | Users cannot view or configure any data collection integrations, including feed and automation integrations, on the **Data Sources & Integrations** page.                                                                                                                                                                                                                                                                                        | SOC Tier-1 Analyst: Integration configuration is outside Tier-1 responsibilities.                                                                                                                        |
| View       | Read-only access to the **Data Sources & Integrations** page. Users can see integration instances, their status, configuration details, and associated classifiers/mappers.                                                                                                                                                                                                                                                                      | <ul><li>SOC Tier 2 and 3 Analysts: Verify integration status during case response/advanced analysis.</li><li>Threat Hunter: May need to understand data collection sources for threat hunting.</li></ul> |
| View/Edit  | <p>Full control over integration configurations. Users can create, modify, and delete integration instances, manage credentials, and configure classifiers and mappers for data ingestion.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>Users can view the <strong>Credentials</strong> page, but cannot edit it without the Credentials View/Edit permission.</p></div> | Security Engineer: Primary responsibility for configuring integrations.                                                                                                                                  |

**Required and recommended permissions**

Managing integrations effectively often requires visibility into overlapping functional areas. Consider adding the following permissions:

| Permission   | Permission Level | Reason                                                                                                                                                      |
| ------------ | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Data Sources | View/Edit        | These are often used together on the **Data Sources & Integrations** page. Strongly recommended.                                                            |
| Marketplace  | View/Edit        | Strongly recommended. Necessary to install new integration content packs. Strongly recommended.                                                             |
| Credentials  | View/Edit        | Strongly recommended for users who need full integration management capabilities, including credential lifecycle management (creation, rotation, deletion). |


---

# 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-agentix/configure-cortex-agentix/users-and-roles-management/roles-management/role-permissions-by-component/configuration-permissions/integrations-instance-permissions.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.