> 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/multi-tenant-central-licensing-management.md).

# Multi-tenant central licensing management

The new central licensing management for MSSP and enterprise multi-tenant allows the MSSP or enterprise to own and manage their child tenants dynamically from the Cortex Gateway. The Cortex Gateway displays the main account with its child tenants and the number of endpoints and GBs available to allocate to child tenants. The Admin user of the main account can add and delete child tenants, edit allocation of resources to child tenants, and change the child tenant subdomain.

The following are the minimum license requirements for central licensing management:

| Option                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| MSSP multi-tenant       | A multi-tenant deployment enables MSSPs to centrally manage multiple tenants and their resources from the Cortex Gateway.                                                                                                                                                                                                                                                                                                                                                                                                               |
| Enterprise multi-tenant | <p>Large enterprises can have many subdivisions and want to manage their tenant allocation and resources centrally from a main tenant while maintaining complete data separation.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>In an enterprise multi-tenant setup, the license specifies a maximum number of child tenants. Once this limit is reached, no additional tenants can be created, even if there remains allocation for endpoints or GBs.</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-xdr-3.x/cortex-xdr-3.x-documentation/multi-tenant/multi-tenant-central-licensing-management.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.