> 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-6-multi-tenant-guides/6.15/configure-multi-tenant/configure-the-multi-tenant-deployment/install-engines-on-tenants-in-a-multi-tenant-deployment.md).

# Install Engines on Tenants in a Multi-Tenant Deployment

Install tenant engines and configure firewall access in Cortex XSOAR 6.15 multi-tenant deployments.

Engines created on tenants use a different encryption handshake for each tenant and connect back to the tenant through the main host server.

1. Configure the base URL.
   1. On the tenant, go to Settings → ABOUT → **Troubleshooting**.
   2. In the **Base URL** field, enter the external tenant URL address in the following format:

      `<main account external address>/<tenant account name>`

      For example, `demisto.com:443/acc_myaccount`
2. Download and install the engine.
   1. Go to Settings → INTEGRATIONS → **Engines**.
   2. Click **Create New Engine**.
   3. Select and download the appropriate installer file.
   4. Install the engine on the appropriate remote machine.
3. Propagate the engine to tenants.
   1. Go to **Settings** → **Integrations** → **Engines**, select the engine, and click **Load-Balancing and Propagation**.
   2. Assign one or more engine propagation labels.
   3. If you want to allow use of the engine for tenant specific integration instances, select **Allow tenants to use this engine for custom integration instances**. If you do not select this option, the engine can only be used with integration instances that were assigned the engine on the main account level and were propagated to tenants.
   4. Go to **Settings** → **Account Management** → **Accounts**, and **Sync** your selected tenant(s).
4. Go to Settings → INTEGRATIONS → **Engines** and verify that the engine is connected.

   In many cases the Cortex XSOAR server has a firewall because the engine is probably installed in a different network. The firewall might stop any communication between the engine machine and the Cortex XSOAR server.

   Ensure that the engine machine is able to communicate with the main host server. You can use Telnet, or any similar tool to check the engine has access to the main account before you install it. If there is a firewall you may need to allow access from the machine that hosts the engine, so that it can communicate back on port 443 (or any other port the main host may use) or set an ANY ANY rule.


---

# 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-6-multi-tenant-guides/6.15/configure-multi-tenant/configure-the-multi-tenant-deployment/install-engines-on-tenants-in-a-multi-tenant-deployment.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.