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

# Sub-Accounts

Sub-accounts split your capital into separate compartments under one master account — one per strategy, each with its own positions, margin and liquidations. They are Hyperliquid sub-accounts: the same non-custodial custody, visible on any Hyperliquid front-end. On Dasus they live at `/subaccounts`, also reachable from the wallet menu in the top bar (the **Sub-Accounts** entry shows how many you have).

## What you can do

Every action below needs a connected wallet with trading enabled ([Enable Trading](https://dasus.gitbook.io/dasus-docs/start-here/enable-trading.md)). They are signed by your trading session key, so there are no wallet popups.

| Action       | How                                                                                                                                                                                                                                                                                                                              |
| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Create**   | **Create sub-account**, give it a name (up to 24 characters, e.g. "BTC strategy") and confirm. Hyperliquid takes a few seconds to index a new one; the list refreshes on its own.                                                                                                                                                |
| **Rename**   | The pencil next to the name.                                                                                                                                                                                                                                                                                                     |
| **Transfer** | **Transfer** on a row moves **perps USDC** between the master account and that sub-account, in either direction — tap the pill to flip the direction. **MAX** fills in what is available on the source side ("Available on master" / "Available on {name}").                                                                     |
| **Trade as** | **Trade** on a row switches your identity to that account and opens the terminal ("Now trading as …"). Clicking the row switches without leaving the page; the active account carries an **Active** badge. The wallet menu lists **Master account**, every sub-account and the vaults you lead, so you can switch from anywhere. |

The table shows each account's **Name**, **Address**, **Perps equity** and **Spot equity** (USDC plus tokens valued at their USDC-pair price), refreshed every 15 seconds. A zero is shown as $0.00.

## While you trade as a sub-account

* The top bar shows **Sub: {name}**. Orders, positions, balances, TP/SL and cancels all belong to that account until you switch back to **Master account**.
* The account panel next to the order form shows the sub-account's figures; the balance in the top bar remains your master account's total.
* [Swap](https://dasus.gitbook.io/dasus-docs/the-app/swap.md) always uses the master account's spot balance.
* Creating, renaming and funding sub-accounts are always sent from the master account, whichever identity is active.

{% hint style="warning" %}
**Dasus's platform fee does not carry over to sub-accounts.** The fee approval you signed is per address, and Hyperliquid rejects an order that carries a builder fee the address has not approved. When that happens Dasus resends the same order without its fee code, so the trade goes through — but it is not charged the Dasus fee, and therefore does not count for referral earnings or cashback.
{% endhint %}

{% hint style="danger" %}
**Careful when copying a sub-account address.** It is generated on Hyperliquid's L1: **do not send funds directly to it or they will be lost.** Always use **Transfer** to move USDC between master and sub-accounts. Dasus reminds you of this every time you copy one.
{% endhint %}

## Related pages

* [Portfolio](https://dasus.gitbook.io/dasus-docs/the-app/portfolio.md) — your equity and tables
* [Funding Your Account](https://dasus.gitbook.io/dasus-docs/start-here/funding-account.md) — deposits, withdrawals and account modes
* [Fees](https://dasus.gitbook.io/dasus-docs/the-app/fees.md) — what each trade costs


---

# 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://dasus.gitbook.io/dasus-docs/the-app/sub-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.
