> 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.12/configure-multi-tenant/manage-content/add-propagation-labels-to-an-existing-tenant-account.md).

# Add Propagation Labels to an Existing Tenant Account

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.12/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.

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 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.12/configure-multi-tenant/manage-content/add-propagation-labels-to-an-existing-tenant-account.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.