> 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-xsiam/configure-cortex-xsiam/multi-tenant/onboard-cortex-multi-tenant/onboarding-checklist-for-multi-tenant-customer-owned-license-deployments/step-2.-define-access-configuations-and-role-permissions.md).

# Step 2. Define access configuations and role permissions

Configure Customer Support Portal access and Cortex Gateway roles for manual parent-child tenant pairing in Cortex XSIAM.

To set up manual pairing in a customer-owned license multi-tenant deployment, after the parent and child Cortex XSIAM tenants are activated, you must define correct access configuration in the Customer Support Portal (CSP) and role permissions in Cortex Gateway.

The following table describes the access configurations and role permissions needed:

| Tenant         | Application                                                                                                                  | Action                                                                                                                                        |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Parent         | Customer Support Portal (CSP) Account                                                                                        | Ensure the parent user name has Super User role permissions.                                                                                  |
| Cortex Gateway | Ensure the user name added to the child tenant’s CSP account has Admin role permissions on the parent Cortex XSIAM instance. |                                                                                                                                               |
| Child          | Customer Support Portal (CSP) Account                                                                                        | Add the user name from the parent tenant who is initiating the parent-child pairing and ensure the user name has Super User role permissions. |
| Gateway        | Provide the user name added in CSP with Admin role permissions to access the child Cortex XSIAM instance.                    |                                                                                                                                               |


---

# 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-xsiam/configure-cortex-xsiam/multi-tenant/onboard-cortex-multi-tenant/onboarding-checklist-for-multi-tenant-customer-owned-license-deployments/step-2.-define-access-configuations-and-role-permissions.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.