> 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-xsoar-6-multi-tenant-guides/6.15/configure-multi-tenant/manage-content/add-propagation-labels-to-content.md).

# Add Propagation Labels to Content

Apply propagation labels to control content synchronized to tenant accounts in Cortex XSOAR 6.15.

You can add propagation labels when creating a new content item or when editing an existing item.

The default propagation label for all content items is **All**.

{% hint style="info" %}
We recommend that you first apply propagation labels to your tenant accounts and then add the corresponding labels to the content items that you want to sync to the tenants.
{% endhint %}

The following content items support propagation labels:

* Playbooks
* Scripts
* Integrations
* Indicator fields
* Incident fields
* Evidence fields
* Indicator types
* Incident types
* Pre-process rules
* Lists
* Widgets
* Dashboards
* Incident layouts
* Indicator layouts

{% hint style="info" %}

### Note

When installing a content pack from the Marketplace, the default propagation label is set to `all`. If you want to change the propagation label, after installation, go to the **INSTALLED CONTENT PACKS** tab and click the propagation button. If a content item is part of a content pack and it is not specifically labeled, it inherits the content pack’s propagation labels. If labels are specified, it propagates according to those labels.

For a non-content item such as an integration instance, if you want to propagate the instance, you need to apply propagation labels both to the integration and to the instance. If a tenant does not have the integration installed, the instance will not be propagated even if the propagation label exists both on the main account and tenant account.
{% endhint %}

If you want to create new propagation labels, or add existing ones, ensure that you have the required [permissions](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/users-and-roles/roles-in-cortex-xsoar/role-based-permission-levels.md).

1. Go to the content item that you want to add a propagation label to.
2. In the **Propagation Labels** field, add the relevant labels.
   * Select an existing label.
   * Type a new label and press **Enter**. The label is immediately available to select in the platform.
   * Keep the **All** label to sync this content item to all tenant accounts.


---

# 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-xsoar-6-multi-tenant-guides/6.15/configure-multi-tenant/manage-content/add-propagation-labels-to-content.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.