> 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-8-saas/multi-tenant/child-tenant-management/content-management-in-multi-tenant/add-propagation-labels-to-content.md).

# Add propagation labels to content

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" %}

### Tip

We recommend that you first apply propagation labels to your child tenants 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 and integration instances
* Indicator fields, types, and layouts
* Incident fields, types, and layouts
* Threat Intel Report types, fields, and layouts
* Classifiers and mappers
* Evidence fields
* Pre-process rules
* Lists
* Widgets
* Dashboards

{% hint style="info" %}
When installing a content pack from 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 on the **Marketplace** page and click the propagation button for the content pack. If a content item is part of a content pack and 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 integration 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 tenant and child tenant.
{% endhint %}

If you want to create new propagation labels or add existing ones, ensure that you have the required permissions. For more information, see [Role-based permissions in Cortex XSOAR](/cortex-xsoar-8-saas/configure-cortex-xsoar/users-and-roles-management/roles-management/role-based-permissions-in-cortex-xsoar.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 by either selecting an existing label or typing a new label. After typing a new label and pressing **`Enter`**, the label is available immediately for use. If you instead keep the default **`all`** label, the content syncs to all child tenants. For example, when editing or creating a playbook, in the **PLAYBOOK SETTINGS** section, in the **Propagation Labels** field, add the label as required.


---

# 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-xsoar-8-saas/multi-tenant/child-tenant-management/content-management-in-multi-tenant/add-propagation-labels-to-content.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.