> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/core/workspace-administration/entities/delete-an-entity.md).
# Delete an entity
{% hint style="success" %}
This article is for Administrators only.
{% endhint %}
## Overview
* You can delete an entity if you don't use it.
* All accounts, members and groups linked to the entity will automatically be unlinked. They won't be deleted.
* Deleting an entity is a permanent action that can't be undone.
## Instructions
1. Go to the **Entities** tab at the top of the Accounts page.
2. Click the name of the entity you want to delete.
3. Click **Delete** next to the entity's name.
4. After carefully reviewing the warning, click **Confirm** to finalize the request.
## Results
A *Delete entity* request is submitted for approval to all Administrators in the workspace. They do not need their device to approve the request.
## What's next?
The entity will be deleted once the request is approved by the number of Administrators defined in the admin rule. All accounts, members and groups linked to the entity will automatically be unlinked.
## See also
* Edit an entity
* Unlink an account from an entity
---
# 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://help.enterprise.ledger.com/core/workspace-administration/entities/delete-an-entity.md?ask=&goal=
```
`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.