> 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/marketplace-permissions.md).

# Marketplace permissions

Control access to discover, install, and manage Marketplace content packs in Cortex XSIAM.

Configure access to manage content packs in Marketplace.

Marketplace is the central hub for discovering, installing, and managing content packs in Cortex XSIAM. Content packs include integrations, playbooks, scripts, dashboards, and other automation content that extend capabilities. Installing a content pack is typically the first step; further configuration of the included integrations or credentials must be completed in the Configurations section.

{% hint style="warning" %}

### Caution

Granting View/Edit access to the Marketplace allows users to install new content packs. As content packs often contain Python scripts and automated playbooks, this permission effectively allows users to introduce new executable code into the tenant. This should be restricted to Security Engineers and Administrators.
{% endhint %}

| Permissions | Description                                                                                                                                         | Roles Example                                                                                                                  |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| None        | No access to the Marketplace, and users cannot view content packs.                                                                                  |                                                                                                                                |
| View        | Read-only access to browse, search, and view pack details and version history.                                                                      | SOC Tier 1, 2, and 3 Analysts, and Threat Hunters: Browse available content and reference content packs during investigations. |
| View/Edit   | Full access to install, uninstall, upload, and upgrade content packs. Users can also contribute content from other pages (e.g., scripts/playbooks). | Security Engineer: Full content management, including custom contributions.                                                    |

**Required and recommended permissions**

Consider adding the following permissions:

| Permission   | Permission Level | Reason                                                                      |
| ------------ | ---------------- | --------------------------------------------------------------------------- |
| Integrations | View             | Strongly recommended to view and configure installed integration instances. |
| Playbooks    | Enabled          | Recommended to view installed playbooks.                                    |
| Scripts      | Enabled          | Recommended to view installed scripts.                                      |
| Credentials  | View             | Strongly recommended to configure integration credentials.                  |


---

# 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/marketplace-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.