> 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/edit-an-entity.md).

# Edit an entity

{% hint style="success" %}
This article is for Administrators only.
{% endhint %}

## Overview

* You can edit an entity to change its name and add or remove accounts.

## Instructions

1. Go to the **Entities** tab at the top of the Accounts page.
2. Click the entity name.
3. Click **Edit** next to the entity's name.
4. (optional) Edit the **Entity name** .
5. (optional) Add or remove **Entity accounts** .
6. Click **Next** .
7. Click **Edit entity** to finalize the request.

<figure><img src="/files/TO0Ai6uSXN9LAQZUyA4i" alt=""><figcaption></figcaption></figure>

## Results

An *Edit entity* request is submitted for approval to all Administrators in the workspace. They do not need their device to approve the request. The new entity will be active when the necessary number of approvals is collected.

## What's next?

Your changes will be implemented once the request is approved by the number of Administrators defined in the admin 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 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/edit-an-entity.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.