> 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-xdr-3.x/cortex-xdr-3.x-documentation/multi-tenant/onboard-cortex-multi-tenant/onboarding-checklist-for-multi-tenant-customer-owned-license-deployments/step-3.-pair-a-parent-tenant-with-child-tenant.md).

# Step 3. Pair a parent tenant with child tenant

After you set up the correct access configurations and role permissions, you should pair the parent tenant to the child tenants.

**Pairing a Parent and Child Tenant**

1. Log in to the Cortex XDR tenant that has been assigned as the parent tenant and select Settings → Configurations → **Tenant Management**.

   The Tenant Management table displays:

   * **Tenant Name**: Name of the child tenant.
   * **Pairing Status**: State of a pairing request: **Paired**, **Pending**, **Failed**, **Rejected**.
   * **Account Name**: CSP account to which the child tenant is associated.
   * **Last Sync**: Timestamp of when the parent tenant last made contact with child tenant.
   * **Managed Security Actions**: A column for each security action with a status: **Configuration name** or **Unmanaged**. **Unmanaged** status means that a configuration for the security action has not yet been selected.
2. Click **+ Pair Tenant**.
3. In the **Pair Tenant** window, select the child tenant you want to pair. The dropdown only displays child tenants your are allowed to pair with.

   Child tenants are grouped according to:

   * **Unpaired**: Children that have not yet been paired and are available. If another parent has requested to pair with the child but the child has not yet agreed, the tenant will appear.
   * **Paired**: Children that have already been paired to this parent.
   * **Paired with others**: Children that have been paired with other parents.
   * **Pending**: Children with a pending pairing request.
4. **Pair the tenant.**

   Cortex XDR sends a **Request for Pairing** to the specified child tenant.
5. In the child tenant Cortex XDR console, a child tenant user with Admin role permissions needs to approve the pairing by navigating to **Notifications** ![notification-icon.png](/files/6AUAoHZxsgTFyb9xPYUx), locate the **Request for Pairing** notification and select **Approve**.
6. Verify the parent-child pairing.

   After pairing has been approved, in the child tenant’s Cortex XDR app, when navigating to a page managed by a parent configuration, the child user is notified by a flag who is managing their security.

   In the child tenant’s, pages that you manage, appear with a read-only banner. Child tenant users cannot perform any actions from these pages, but can view the configurations you create on their behalf.

   ![child-managed-read-only-banner.png](/files/gsRfMWlFfoB2xMFGFozF)


---

# 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-xdr-3.x/cortex-xdr-3.x-documentation/multi-tenant/onboard-cortex-multi-tenant/onboarding-checklist-for-multi-tenant-customer-owned-license-deployments/step-3.-pair-a-parent-tenant-with-child-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.