> For the complete documentation index, see [llms.txt](https://docs.squads.so/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squads.so/main/navigating-your-squad/treasury/sub-accounts.md).
# Sub-accounts
Learn how to use sub-accounts in Squads.
Sub-accounts are separate vaults that users can create to better manage their treasury assets such as payroll, marketing expenses, NFT holdings, etc.
Each sub-account has its own SPL address and inherits the multisig setup of its Squad.
{% hint style="info" %}
Sub-accounts are only accessible to users with a Squads Business or Enterprise plan. Learn more about our pricing and subscription plans [here](/main/getting-started/pricing.md).
{% endhint %}
### **Inside a sub-account, users can:**
* Initiate deposits, withdrawals, and swaps
* Create contacts for quick access when withdrawing treasury assets
* Check SPL tokens and NFTs held, as well as their respective weight in the overall account balance
* Quickly stake their SOL holdings by clicking on the “Stake” button next to the SOL asset
* Check the inflows and outflows of the sub-account
Sub-accounts
---
# 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.squads.so/main/navigating-your-squad/treasury/sub-accounts.md?ask=&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.
