> 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.14/configure-multi-tenant/configure-the-multi-tenant-deployment/add-a-tenant-to-a-host.md).

# Add a Tenant to a Host

A tenant, or account, is a single instance of Cortex XSOAR that you connect to a host. You populate tenants with users by specifying user roles. Any user who belongs to a selected role is automatically added to the account. All nested roles (both directions) must be explicitly assigned. Users cannot access data on a tenant unless they have a role assigned to that tenant. When you create the tenant account you can specify the propagation labels, which determines which content items are eligible for [syncing to the tenant](/cortex-xsoar-6-multi-tenant-guides/6.14/configure-multi-tenant/manage-content/sync-content-to-tenant-accounts.md).

{% hint style="info" %}

### Note

When adding a role, by default, the administrator with read and write permissions is added automatically.
{% endhint %}

Each tenant machine must meet the [multi-tenant sizing requirements](/cortex-xsoar-6-multi-tenant-guides/6.14/learn-about-mult-tenant/plan-your-multi-tenant-deployment/multi-tenant-sizing-requirements.md).

1. In Cortex XSOAR, go to Settings+ACCOUNT MANAGEMENT → **Accounts**.
2. Click the **Add account** button.
3. Enter a meaningful name for the account.

   The account name cannot contain white space.
4. Choose the host or high availability group.
5. (Optional) Select existing propagation labels or type new propagation labels.
6. Select at least one role to add to the account.

   The administrator with read and write permissions is added to the account by default. You can change this if required.
7. Click **Create account**.

You can access the tenant account via the main account URL or via the host URL, depending on your specific needs. If you access a tenant account via the main account, the main account must have a public URL. If you access a tenant account via the host, the host must have a public URL. Keep in mind that if you access the tenant account via the host URL, the entry will not be recorded in the main account.

In the Main Account, you can also select which tenant account’s dashboard, incidents, and indicators (Threat Intel page) to view and take action as necessary without having to switch accounts. This enables you to view information quickly and more efficiently.

Location may be a factor when planning how to access accounts. If a user is in Europe, the main account is in the United States, and the tenant account is in Europe, accessing the tenant account through the main account requires going from Europe to the United States and back to Europe, and is less efficient than directly accessing the host URL.

{% hint style="info" %}

### Note

To delete a tenant, go to **Settings** → **ACCOUNT MANAGEMENT** → **Accounts** . Select the tenant, **Stop** the tenant, and then **Delete account**.
{% endhint %}


---

# 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-6-multi-tenant-guides/6.14/configure-multi-tenant/configure-the-multi-tenant-deployment/add-a-tenant-to-a-host.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.