> 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/onboard-cortex-xsoar-multi-tenant/step-2.-pair-child-tenant-to-main-tenant.md).

# Step 2. Pair the child tenant to main tenant

After installation of the main tenant and child tenants, pairing is required to facilitate a multi-tenant system. Tenant pairing enables resource optimization between the tenants, enhanced security by providing isolation and granular access control to the child tenants, and flexible distribution of content.

To pair the tenants, you must have a network connection, the child tenant URL and the child pairing token. In the main tenant, go to the **Tenant Management** page to pair the child tenant. When pairing is established, you can begin to add users, roles, and distribute content. If the tenants are not paired, the tenants cannot communicate, and content is not updated or distributed to the child tenants.

**Pairing a child tenant to the main tenant:**

1. Log in to the Cortex XSOAR child tenant. When logging into the child tenant for the first time, a pairing token is generated for pairing the child tenant to the main tenant:

   ![child\_pair\_with\_main\_login\_screen.png](/files/xFYB6umDAKkT4eKmV20p)

   Click the **Copy Pairing Details** to copy the child URL and pairing token to paste in the main tenant.
2. Log in to the Cortex XSOAR main tenant and select Settings → Configurations → **Tenant Management**.

   The Tenant Management table displays:

   * **Tenant Name**: Name of the child tenant.
   * **Status**: State of a pairing request: **Paired**, **Pending**, **Failed**, **Rejected**.
   * **Last Sync**: Timestamp of when parent tenant last made contact with child tenant.
   * **Propagation Labels**: Either All or custom propagation labels are listed for syncing content to the child tenant.
   * **Pair Date**: Timestamp of when pairing occurred.
3. Click **Pair new tenant**. Paste the details from the child tenant:

   ![pair\_new\_tenant.png](/files/ldim61nUbfsKnYHFyquz)

   Cortex XSOAR sends a **Request for Pairing** to the specified child tenant.
4. Verify the parent-child pairing.

   In the **Tenant Management** page, the status of the pairing request is shown.

   If a child tenant disconnects from the main tenant, a banner at the top of the page shows that a child tenant is disconnected. If this happens, re-pair and sync the content of the child tenant from the **Tenant Management** page.


---

# 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/onboard-cortex-xsoar-multi-tenant/step-2.-pair-child-tenant-to-main-tenant.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.