> 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/marketplace/manage-content-packs.md).
# Manage content packs
Install, update, revert, and delete Cortex Marketplace content packs and manage required and optional dependencies in Cortex AgentiX.
Manage Cortex Marketplace content packs in Cortex AgentiX. Install, update, revert, or delete content packs. Before installation, review each content pack’s included integrations, scripts, playbooks, and dependencies.
For each Marketplace content pack, you can view:
* **Details:** General information about the content pack such as installation, content, version, author, and status.
* **Content:** The content to be installed, such as scripts or integrations.
* **Dependencies:** Details of any required content packs and optional content packs that may need to be installed with your content pack.
* **Version History:** View the currently installed version, earlier versions, available updates, and revert if required.
### Content pack dependencies
In Cortex AgentiX content packs, some objects depend on other objects. For example, an issue may depend on a playbook, issue type, and issue field. A script may depend on another script or integration. When you add a content pack to your cart, required content packs and mandatory dependencies are added automatically. This ensures the content pack installs correctly.
Optional content packs support the content pack you want to install. They are not required for installation. When you add a content pack to your cart, select any optional content packs you need. Required dependencies for selected optional content packs are included automatically.
{% hint style="info" %}
### Note
Optional content packs that are already installed are treated like they are required content packs to preserve content integrity.
{% endhint %}
Install a Cortex Marketplace content pack
You can install one Cortex Marketplace content pack at a time. Cortex AgentiX automatically adds required content and dependencies. You can also add optional content packs used by the selected content pack.
If you receive an error message when you try to install a content pack, you need to fix the error before installing. If a warning message is issued, you can still download the content pack, but you should fix the problem; otherwise, the content may not work correctly.
{% hint style="info" %}
### Note
Cortex AgentiX includes a built-in default mail sender. You also have the option of installing a different mail sender content pack, such as [Microsoft Exchange Online](https://cortex.marketplace.pan.dev/marketplace/details/MicrosoftExchangeOnline/).
{% endhint %}
1. Go to Settings → **Configurations** → **Marketplace** → **Browse** and locate the content pack you want to install.
2. Click the required content pack and review the contents.
3. Click **Install** to add the content pack to the **Cart**.
4. (Optional) If the content pack includes optional content, select the content packs you want to add.
The **Cart** displays the number of items you are installing, including any required content packs. You can log in and out, but the content packs remain in the **Cart** until you click either **Empty cart** or **Install**.
5. Click **Install**.
6. After installation, click **Refresh content**.
{% hint style="info" %}
### Note
In addition to content packs that you install from Marketplace, related content packs are automatically downloaded when you adopt playbooks or edit tasks that require content items such as scripts or integrations.
{% endhint %}
Update a Cortex Marketplace content pack
Content pack updates deliver bug fixes and enhancements. Cortex Marketplace refreshes every two hours. When an update is available, a notification appears in the **Installed Content Packs** tab.
In the **Version History** tab of a content pack, you can see the currently installed version, earlier versions, and available updates. You can revert to a previous version of a content pack if required.
All dependent content packs update automatically with the content pack.
{% hint style="info" %}
### Tip
You can also find content packs that require updates by going to **Settings** → **Data Sources & Integrations** and filtering by **Pack Version** = **Update Available**. If you click on an integration in the filtered list, there is a link to the content pack in Marketplace for updates.
{% endhint %}
{% hint style="info" %}
### Note
Third-party product integrations are developed and tested against a specific product version. For products that are on-prem or cloud-based with specific API versions, the version developed and tested against will be included in the integration's documentation. Newer versions of the product are not always immediately tested, and it is expected that products maintain API compatibility upon release of newer product versions. When upgrading to a newer product version, it is highly recommended to test the integration in a dev environment before deploying to production.
{% endhint %}
{% hint style="warning" %}
### Caution
If you want to downgrade, any content that depends on the content pack including any customizations may be deleted if it does not exist in the target content pack version.
{% endhint %}
1. In the **Show** field of the **Installed Content Packs** tab, select **Update available** to display the content packs that are available to update.
2. Click the content pack you want to update.
3. In the **Version History** tab of the content pack, view the available updates.
4. Click **Update**. If there is more than one update available, click the version to update.
If you choose to install the latest version it includes the previous version. If you have made any customizations these are included in any update. If any dependencies require updating, these are automatically added.
5. Click **Install**.
6. After the content pack installs, click **Refresh content**.
Revert a content pack to an earlier version
You can revert an installed content pack to an earlier version. Items missing from the target version are also deleted. These items can include detached playbooks or scripts that use content pack scripts. This may cause other content packs to stop working.
1. In the **Installed Content Packs** tab, click the content pack you want to revert.
2. In the **Version History** tab, select the version to which you want to revert.
3. Click **Revert to this version**. The version will be added to your **Cart**.
4. In the **Cart**, click **Downgrade**.
Delete a Cortex Marketplace content pack
When you delete a Cortex Marketplace content pack, all associated content is deleted. This includes detached and customized content.
{% hint style="warning" %}
### Caution
If another content pack is dependent on the content pack you want to delete, it may break the other content pack. You can reinstall the content pack, but you cannot restore detached and customized content.
{% endhint %}
1. Go to Settings → **Configurations** → **Marketplace** → **Installed Content Packs**.
2. In the **Content Packs Library** section, search for the content pack and select the content pack you want to delete.
3. Click the trash can icon.
4. Review the warning message and click **Delete**.
---
# 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-agentix/configure-cortex-agentix/marketplace/manage-content-packs.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.