> 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/help-center-v2/guides/accounts.md).

# Accounts

Guides for working with Accounts on Ledger Enterprise: finding them, reading balances, and creating or editing them.

An Account holds **one asset on one network**, and carries its own governance. A Workspace typically has many, organized by purpose, entity, or counterparty.

<table><thead><tr><th width="286.08203125">Guide</th><th>Role</th></tr></thead><tbody><tr><td><a href="/help-center-v2/guides/accounts/finding-accounts-and-balances.md">Finding Accounts and balances</a></td><td>Everyone</td></tr><tr><td><a href="/help-center-v2/guides/accounts/creating-and-editing-accounts.md">Creating and editing Accounts</a></td><td>Administrators</td></tr></tbody></table>

## How Accounts relate to everything else

* An Account's **Rules** decide who may send from it, who must approve, and to which destinations. Those Rules are either the Account's own or come from a shared [**Policy**](/help-center-v2/guides/governance/policies.md).
* **Token Accounts** attach to a parent Account, which pays their network fees.
* **Linked Accounts** are the same address on other EVM networks, each a separate Account with separate balances and governance.
* **Portfolios** group Accounts for organization and reporting without affecting governance.

## Related

* [**Transactions**](/help-center-v2/guides/transactions.md)
* [**Governance**](/help-center-v2/guides/governance.md)
* [**Networks**](/help-center-v2/reference/networks.md)


---

# 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/help-center-v2/guides/accounts.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.