> 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-on-prem/8.14/multi-tenant/incident-management-on-the-main-tenant/run-a-command-on-multiple-tenants.md).

# Run a command on multiple tenants

In some cases, you might need to run a command across multiple tenants. For example, you might want to enrich certain IOCs across all child tenants.

From the main tenant, you can batch-run a command on incidents from different child tenants. Running a command at the main tenant runs it locally on each child tenant.

If the command doesn’t exist on a particular tenant or if the user running the command from the Main Tenant doesn’t have the correct permissions, the command execution fails and the output is written to the incident’s war room. You will not see the error in the main tenant.

In some cases, child tenants may have different versions of the same command. The local version of the command runs on the child tenant.

1. On the **Incidents** page in the Main Tenant, select one or more incidents.
2. Click **Run Command**.
3. Enter the relevant command and press enter.


---

# 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-on-prem/8.14/multi-tenant/incident-management-on-the-main-tenant/run-a-command-on-multiple-tenants.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.