> 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/sync-content-to-tenant-accounts.md).

# Sync Content to Tenant Accounts

The content that you sync from the Main Account to the tenant accounts might add, override, or remove content from the tenant accounts. New content items, which do not currently exist on the tenants, are added. When you sync content to tenant accounts, there can potentially be content items that will be added.

* **Add**: New content items, those which do not currently exist on the tenants, will be added.
* **Override**: For content items that are being pushed in the sync operation and which already exist on the tenants, the sync operation will override the existing content on the tenant accounts.
* **Remove**: For content items that were removed from the main account and which already exist on the tenant accounts, the sync operation will remove the existing content from the tenant accounts.

It is important that you review each content item and their dependencies before syncing the content. You have the option to remove items before executing the sync operation for a single tenant.

{% hint style="info" %}

### Note

If you are using version control and need to revert to an earlier version of a content item and to push this change to tenant accounts, selective propagation must be enabled.
{% endhint %}

Before you begin, 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) to sync accounts.

1. In the Main Account, go to Settings → **Account Management**.
2. Select one of the following options to sync content.
   1. (Option 1) To review the content you want to sync to a tenant, select the required tenant checkbox and then click **Sync**.
      1. Review all content affected by the sync operation in the **ADD**, **OVERRIDE**, **REMOVE** tabs.
      2. If there are playbooks listed in the **OVERRIDE** tab, select or clear checkbox to **Override playbook inputs** in the tenant account.
      3. If the **Run on** field has changed in the automation, select or clear the **Overwrite automation run-on** to override this field in the tenant account.
   2. (Option 2) To sync content to tenant accounts without manual review, select two or more tenant accounts and then click **Sync**.

      This option automatically updates new, and existing content to the tenant account, and removes outdated content. If there are playbooks and automations select or clear the checkbox to override playbook inputs and the Run on automation field in the tenant account.
3. Click **Sync**.


---

# 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/sync-content-to-tenant-accounts.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.