> 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.13/configure-multi-tenant/manage-content/manage-content-overview.md).

# Manage Content Overview

Content, including integrations, can be configured on the main account or on tenant accounts.

In most cases, if the content applies to all tenants, it should be configured on the main account and pushed to the tenants. In some cases, you may need to configure an integration on the tenant level. For example, you might have a situation where only the customer has the information needed to configure a specific integration and they do not want that information stored at the main account level. In addition, any integration that fetches incidents or indicators (feeds) must be configured on the tenant level, since incidents are not stored on the main account. If an integration has the same settings for multiple tenants, you have the option, with selective propagation, to configure the integration on the main account level and propagate to specific tenants.

In order for a content item to be synced to a tenant account, both the content and tenant account must have the same propagation label.

For example, if you want Playbook ABC to sync to Tenant 123, they both need to have the same propagation label, such as **Premium**.

{% hint style="info" %}

### Note

When using a remote repository with a multi-tenant deployment, the remote repository must be configured and a machine must be set as the development environment, before you can view propagation labels.

If there is no relevant propagation tag on your content, for example, a script or playbook, but it is a dependency of a package that you do propagate to a tenant, the unlabeled content is still synced to the tenant.
{% endhint %}

There are several types of propagation labels that you can use for syncing content to tenant accounts.

* **All**: Content items with the label **all** will be synced to all tenants, whether or not the tenants have labels. This is the default label for content items.
* **Custom**: You can add custom labels by typing a label name in the **Propagation Label** field when adding or editing a content item or a tenant.
* **None**: If a content item does not have any labels, it will not be synced to any tenants. If a tenant does not have any labels, only content items with the **all** propagation label will sync to it.

{% hint style="info" %}

### Tip

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

{% hint style="info" %}

### Note

If you sync a content item from the main account to a tenant account, and a content item with that same name already exists on the tenant account, the content on the tenant account will be overwritten. This applies to integrations, fields, incident types, and Threat Intel report types.

To remove propagation labels, use the API call **`DELETE /propagationlabels/`*****`<label-name>`***.
{% endhint %}


---

# 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-6-multi-tenant-guides/6.13/configure-multi-tenant/manage-content/manage-content-overview.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.