> 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/onboard-cortex-xdr/multi-tenant/child-tenant-management/pairing-accesss-control.md).

# Pairing accesss control

Pairing access control in Cortex XDR allows child tenant administrators to manage and restrict a paired parent tenant's permissions and data scope.

Pairing access control is a security model for MSSP/MT tenant pairing that gives child tenants control over the access a paired parent tenant has into their environment. When a main tenant pairs with a child tenant, Cortex XDR automatically generates an API key on the child tenant that represents that pairing. With pairing access control enabled, this pairing API key is assigned a dedicated system role, **Pairing Key**.

Administrators at the child tenant, the managed organization, can view this pairing key in **Settings > Configuration > API Keys**, and can change its role and access scope, without affecting the underlying pairing itself.

{% hint style="info" %}
**NOTE**

Pairing access control is not enabled by default. Contact Customer Support to enable this feature for your tenant.
{% endhint %}

### Benefits of pairing access control

Pairing access control gives child tenant administrators direct control over what a paired parent tenant can access, through the pairing API key that represents that connection:

* **Curated set of permissions**: New pairing keys are assigned the **Pairing Key** role, which grants the operations typically needed for parent-to-child activity.
* **Control over permissions and data scope**: Child tenant administrators can edit the **Pairing Key** role's permissions, and edit the pairing key’s API settings directly to narrow which data the pairing key can access to match their own requirements. When the pairing key is first created, its data access scope starts out unrestricted; the child tenant administrator can then narrow that data scope afterward, independently of the role's permissions.

### Comparison

| **Aspect**                                | **Pairing access control not enabled (default)** | **Pairing access control enabled**                                                                    |
| ----------------------------------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |
| Role assigned                             | Administrator                                    | Pairing Key                                                                                           |
| Permission grant                          | Full administrator permissions                   | A curated set of permissions covering the operations typically needed for parent-to-child activity.   |
| Visibility in API Keys table              | Hidden from the standard API Keys view           | Visible in **Settings > Configuration > API Keys.**                                                   |
| Initial data access scope                 | Not scope-restricted                             | Unrestricted (Scope-Based Access Control (SBAC) full access), narrowed by the child tenant as needed. |
| Role permissions editable by child tenant | No                                               | Yes                                                                                                   |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xdr/onboard-cortex-xdr/multi-tenant/child-tenant-management/pairing-accesss-control.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
