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

# Run a command on multiple tenants

Run commands across tenants in Cortex XSOAR 8.13 On-prem.

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