> 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-saas/multi-tenant/onboard-cortex-xsoar-multi-tenant/step-2.-create-a-child-tenant.md).

# Step 2. Create a child tenant

After you have set up the main tenant, you can set up child tenants in Cortex Gateway. You can create as many child tenants as you require, subject to your license.

{% hint style="info" %}

* The Main Account (main tenant) is labeled in the Cortex Gateway, but child tenants are not labeled.
* Cortex enables parent-child pairing between tenants located in different geographical regions. To enable this capability, contact your support team.
* To create a child tenant, ensure that you have Account Admin permissions.
  {% endhint %}

In Cortex Gateway, you can view all the available tenants. If you want to create more child tenants than your license permits, contact Customer Support.

1. In Cortex Gateway, hover over the main tenant you activated previously, on the right-hand side, click the ellipsis, and then click **Add Child Tenant**.

   ![mt-activation.png](/files/jdvKWb6CkbJ8yz2yHAId)
2. Add the following details.

   | Parameter                   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
   | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | Child Tenant Name           | <p>Give the Cortex XSOAR tenant an easily recognizable name.</p><p>Choose a name that is 59 or fewer characters and is unique across your company account.</p>                                                                                                                                                                                                                                                                                                                                                   |
   | Region                      | View the region for the child tenant. This can't be changed.                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
   | Child Tenant Subdomain      | <p>Give your Cortex XSOAR instance an easy-to-recognize name that is used to access the tenant directly using the full URL.</p><p>https\://\<subdomain>.crtx.<<em>region</em>>.paloaltonetworks.com</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>This is a public FQDN, so be careful with sensitive information such as the company name.</p><p>After activating a child tenant, you can't change the child tenant Subdomain.</p></div> |
   | Incident Retention Licenses | <p>If you have incident retention licenses available, assign one or more incident retention licenses to the child tenant. For more information, see <a href="/pages/dv3dAocWdMzjJnbfN9Kt">Step 3. Allocate incident retention licenses</a>.</p><p>Click the box to verify you understand that licenses cannot be removed or reallocated without contacting Customer Support.</p>                                                                                                                                 |
3. **Activate** the child tenant and confirm approval.

   Activation can take up to an hour. You should receive notification by email that the child tenant has completed the activation process.
4. (Optional) Add another child tenant by repeating step 2 or access your newly created tenant.

   In the Cortex Gateway, under your main tenant, you can see the total number of tenants you are licensed for and how many you have created.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>If you reach your limit for child tenants, depending on your license, you may be able to create more tenants. You may be charged for additional tenants. Contact Customer Support if you are approaching your authorized limit.</p></div>


---

# 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-saas/multi-tenant/onboard-cortex-xsoar-multi-tenant/step-2.-create-a-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.
