> 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/delete-a-tenant-from-a-host.md).

# Delete a Tenant From a Host

Delete a tenant account from a host through Account Management in Cortex XSOAR 6.15.

If you do not want to use a tenant account (temporarily or permanently), on the **ACCOUNT MANAGEMENT** page (**Settings** → **ACCOUNT MANAGEMENT**), you have the following options:

* Start/stop a tenant: The tenant is not deleted from the database, but you cannot access the account from the port. Used when you want to reindex a single tenant.
* Block/unblock a tenant: Blocks/unblocks the account at the proxy level (you can still access the tenant via the port). Used temporarily to fix an issue with a tenant.
* Delete a tenant: Removes the tenant from the database.

{% hint style="warning" %}
In an Elasticsearch environment, when deleting an account, although the tenant's data is not deleted, the Elasticsearch indices will be closed. Another tenant with the same name cannot be created until the indices are opened or deleted. If you try to create a tenant, the following message is displayed:

`Failed to create tenant [%s]. There are closed ES indices of former account with the same name`
{% endhint %}

1. Go to **Settings** → **ACCOUNT MANAGEMENT** and select the tenant you want to remove.
2. Click Delete account.
3. In the dialog box, type the name of the account.
4. Delete the account.


---

# 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/delete-a-tenant-from-a-host.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.