> 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-an-existing-tenant-account.md).

# Add Propagation Labels to an Existing Tenant Account

Add propagation labels to tenant accounts to control content synchronization in Cortex XSOAR 6.15.

The propagation labels that you add to the tenant account determine which content items are eligible for syncing. This information is intended for existing tenant accounts. You can also add propagation labels when you [add a tenant to a host](/cortex-xsoar-6-multi-tenant-guides/6.15/configure-multi-tenant/configure-the-multi-tenant-deployment/add-a-tenant-to-a-host.md).

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

1. In Cortex XSOAR, go to Settings → Account Management → **Accounts**.
2. Choose the tenant that you want to add propagation labels to and click **Roles and propagation**.
3. Select existing propagation labels or type new propagation labels.


---

# 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-an-existing-tenant-account.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.