> 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-5.x/onboard-cortex-xdr/multi-tenant/child-tenant-management.md).

# Child tenant management

Track, manage, and investigate child tenant data from the parent tenant.

You can manage, track, and investigate child tenant data from the parent tenant.

**Manage a child tenant**

Multi-tenancy enables you to view and investigate Cortex XDR data of a child tenant, and initiate security actions on their behalf.

In your Cortex XDR management console, you have access to view the following pages:

* Incidents
* Alerts
* Query Builder
* Query Center and Results
* Causality View
* Timeline View

To initiate security actions on your child tenant, you need to create a **Configuration**. Security actions are managed by configurations you create in Cortex XDR and then assign to each of the child tenants. Each action requires its own configuration and allocation to a child tenant.

{% hint style="info" %}

### Note

Once a configuration is created Cortex XDR resets the child tenant data and synchronizes the security actions configured in the parent tenant.
{% endhint %}

You can create configuration for the following actions:

* BIOC Rules & Exceptions
* Starred Alerts Policies
* Alert Exclusions
* Profiles
* Allow/Block Lists


---

# 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-5.x/onboard-cortex-xdr/multi-tenant/child-tenant-management.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.