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

# Manage funded accounts

After you win a funded account, open the funded **Terminal** to trade it. Each account has its own size, profit split, and trading rules.

## Equip and select an account

1. Open the funded **Terminal**.
2. Choose an account from your **Inventory** and equip it if needed.
3. Select the equipped account you want to trade.
4. Review its rules and remaining loss allowance before opening a position.

Inventory has unlimited capacity. You can equip up to three accounts at once. A new account can auto-equip if a slot is free; additional accounts go into Inventory.

## Switch accounts

Swap between equipped accounts in the funded Terminal. It displays one selected account at a time.

Switching leaves positions on other equipped accounts open. Monitor every account with open positions. Close all of an account's positions before unequipping it.

## If an account breaches

Reaching either loss limit ends the account. Trading stops, and earnings left on it are void under the account rules. You do not owe the lost funded capital.

See [Drawdown rules](/docs/funded/drawdown.md) and [Profit split and payouts](/docs/funded/payouts.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.size.club/docs/funded/manage-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.