> 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-8-on-prem/8.11/multi-tenant/child-tenant-management.md).

# Child tenant management

After you have set up and configured Cortex XSOAR multi-tenant you can manage the following:

* Manage investigations: From the main tenant, you can see all tenants' incidents and indicators. You do not need to switch between tabs or screens to view data for child tenants. You can also pivot to any child tenant, subject to permission for those tenants.
* Run a command on multiple tenants: Run a batch command on the main tenant for all child tenants.
* In the main tenant, you can pivot to a child tenant from specific pages, such as Incidents, and Dashboards. For example, on the **Dashboards** page, click **Main Tenant** and then click the child tenant you want to navigate to.

In Cortex XSOAR, you can use the **Tenant Management** for the following options:

* Add propagation labels to child tenants, remote repositories, and content, and then sync the content from the main tenant to child tenants.
* Pair the main to a child tenant. In **Pair new tenant**, add the child tenant URL, the pairing token copied from the child tenant, and the tenant name, which must be unique.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>During the pairing process, content is not synced.</p></div>
* Unpair a connected child tenant from the main tenant. The status of the child tenant changes to **Unpaired**. If you click the child tenant link from the main tenant, you are navigated to the **Pair with main** screen of the child tenant. You might need to re-login to the child tenant to access the **Pair with main** screen.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>You cannot use a child tenant unless it is paired to the main tenant.</p></div>

  You can click **Remove** to remove the tenant from the list of tenants in **Tenant Management**. If you want to pair the child tenant back to the main tenant after it's been removed, you must **Pair new tenant**. The tenant name and tenant URL remains the same.
* Re-pair a child tenant where status is **Unpaired**.
* Select **Sync** to sync content from the main tenant to the selected child tenant. You can also sync content to all tenants by selecting **Sync all tenants**.
* In case of a potential security issue, you can disconnect a child tenant from the main tenant. This option revokes the valid pairing token and generates a new token for the child tenant. From the child tenant go to Settings → System → **Security Settings** and from **Revoke access to tenant**, click **Revoke**. The pairing token remains active for 24h before a new token is generated. The status of the child tenant in the main tenant updates to **Unauthorized**. To repair the child tenant, from the child tenant go to Settings → System → **Security Settings** and from **Pair with main tenant**, click **Copy Pairing Token**. In the main tenant, select the child tenant and click **Re-Pair Token** and paste the pairing token. The status is updated to **Paired**.
* If a child tenant is not available, the connection between the main and child tenant becomes **Disconnected**. Content is propagated to the child tenant once the child tenant is reconnected to the main tenant and **Sync** is selected.


---

# 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-8-on-prem/8.11/multi-tenant/child-tenant-management.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.