> For the complete documentation index, see [llms.txt](https://docs.allocations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allocations.com/why-allocations/accounts.md).

# Accounts

Accounts group your deals and entities. Use this screen to create accounts and see what each one holds.

Each account belongs to one manager or organization. Create the account before you set up a deal, because Setup asks you to attach the deal to an account.

![](https://content.gitbook.com/content/9IirLidzibYpEfSBave3/blobs/irPLGC8PVDvLrwS04aBW/Unknown%20image)

1. **Total accounts** Counts the accounts set up in the workspace.
2. **Search** Finds an account by typing any part of its name.
3. **Filter** Opens the filter panel for narrowing the list by deal or entity.
4. **Toolbar** Lets you refresh the list, export it, or create an account.
5. **Column headers** Sort the table by Name, Deals, Entities, or Created when selected.
6. **Deals and Entities** Count the deals and entities attached to each account.
7. **Actions** Opens the menu of actions available for that account, such as editing it.

### Why accounts come first

Three parts of the platform use accounts:

* Setup attaches each deal to an account.
* Taxes uses Partnership Representative defaults set on the account.
* Entities are grouped by 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://docs.allocations.com/why-allocations/accounts.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.