> For the complete documentation index, see [llms.txt](https://docs.panther.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.panther.com/detections/panther-managed/content-catalog/updating-catalog-items.md).

# Updating Catalog items

{% hint style="warning" %}
The [Content Catalog](/detections/panther-managed/content-catalog.md) is in closed beta as of Panther version 1.125. To request access, contact your Panther support team.
{% endhint %}

## Overview

Panther periodically releases new versions of the items available in the [Content Catalog](/detections/panther-managed/content-catalog.md). When a new version is available for an item you have installed, the Content Catalog will surface an update on the **Installed** tab. Updating applies the new version to your installed copy in place—the item's identity and the rest of your environment are preserved.

## When updates are available

An update is available for an installed item when both of the following are true:

* A newer version of that item exists in Panther's content releases.
* Panther can apply the new version to your installed copy without producing a merge conflict with edits you have made, and without causing any unit tests to fail.

If either of these conditions cannot be met, an update is not currently available for that item.

{% hint style="info" %}
Support for resolving merge conflicts and failing unit tests directly in the Panther Console will be added in a future Panther release. Until then, if you would like to take an update that is currently unavailable, you will need to reconcile the differences manually—for example, by editing the installed item so that the new version no longer conflicts.
{% endhint %}

## How to update a single Content Catalog item

To update one installed item:

1. In the left-hand navigation bar of your Panther Console, click **Catalog**.
2. Click the **Installed** tab.
3. Locate the item you want to update.
4. In that item's row, click **Update**.

Panther merges the newest version to your installed copy. The item stays in place, its version metadata advances to the new version, and future updates will surface in the same way.

You must have the modify permission for the item's type to update it. See [Required permissions](/detections/panther-managed/content-catalog.md#required-permissions) for details.

## How to update all Content Catalog items at once

The **Installed** tab includes an **Update All** banner that you can use to apply every available update in a single job.

To update all eligible items at once:

1. In the left-hand navigation bar of your Panther Console, click **Catalog**.
2. Click the **Installed** tab.
3. In the banner at the top of the page, click **Update All**.

The update job runs in the background. You can navigate away from the page while it runs—Panther will send an [in-Console notification](/system-configuration/notifications.md) when the job finishes, summarizing what was updated.

{% hint style="info" %}
Only one **Update All** job can run at a time per Panther instance. If a job is already running, you will need to wait for it to finish before starting another.
{% endhint %}

**Update All** applies updates only for items that are currently eligible for update. Items with merge conflicts or failing unit tests are skipped, and remain available for you to address individually.


---

# 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:

```
GET https://docs.panther.com/detections/panther-managed/content-catalog/updating-catalog-items.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.