> 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.14/configure-multi-tenant/manage-content/add-propagation-labels-in-remote-repositories.md).

# Add Propagation Labels in Remote Repositories

If you are working with [Remote Repositories for Multi-Tenant Deployments](/cortex-xsoar-6-multi-tenant-guides/6.14/configure-multi-tenant/remote-repositories-for-multi-tenant-deployments.md), and want to use selective propagation to [Add Propagation Labels to Content](/cortex-xsoar-6-multi-tenant-guides/6.14/configure-multi-tenant/manage-content/add-propagation-labels-to-content.md), you will need to use the following remote repository deployment setup, and follow the steps described in this task.

**Required Remote Repository Deployment Setup**

* **Development environment**. Single, standalone instance of the Cortex XSOAR server (NOT multi-tenant). See [Configure a Remote Repository on a Development Machine](/cortex-xsoar-6-multi-tenant-guides/6.14/configure-multi-tenant/remote-repositories-for-multi-tenant-deployments/configure-a-remote-repository-on-a-development-machine.md) for more information on how to set this up.
* **Production environment**. Multi-tenant deployment, with a main account and tenant accounts, with the main account serving as the sole connection point to the remote repository. See [Configure a Remote Repository on the Main Account](/cortex-xsoar-6-multi-tenant-guides/6.14/configure-multi-tenant/remote-repositories-for-multi-tenant-deployments/configure-a-remote-repository-on-the-main-account.md) for more information on how to set this up.

1. In the development environment, ensure that propagation labels (selective propagation) are enabled.
   1. Go to Settings → About → **Troubleshooting**.
   2. In the **Server Configuration** section, click **+Add Server Configuration**.
   3. Add the following server configurations and set their keys to **`true`**.

      **`selective.propagation.enabled`**

      **`selective.propagation.force`**
2. In the development environment, [Add Propagation Labels to Content](/cortex-xsoar-6-multi-tenant-guides/6.14/configure-multi-tenant/manage-content/add-propagation-labels-to-content.md) as needed.
3. In the development environment, make whatever content changes are needed, and then [push content to the remote repository](/cortex-xsoar-6-multi-tenant-guides/6.14/configure-multi-tenant/remote-repositories-for-multi-tenant-deployments/edit-and-push-content-to-a-remote-repository.md).
4. In the production environment, [pull content from the remote repository](/cortex-xsoar-6-multi-tenant-guides/6.14/configure-multi-tenant/remote-repositories-for-multi-tenant-deployments/configure-a-remote-repository-on-the-main-account.md).
5. In the production environment, confirm that the propagation labels were added to the content, and that the labels are available for use in Settings → Account Management → Accounts → **Roles and propagation**.


---

# 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.14/configure-multi-tenant/manage-content/add-propagation-labels-in-remote-repositories.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.