> For the complete documentation index, see [llms.txt](https://docs.truvera.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truvera.io/truvera-workspace/team-management/sub-accounts.md).
# Sub-accounts
Sub-accounts allow Truvera's customers to segregate their data within the Truvera platform based on their own customers. Each sub-account can have its own keys, organization profiles, credential designs and verification templates conveniently organized to help with tracking and auditing of the activity performed by each.
In order to easier manage sub-account assets [Ecosystem Tools](/truvera-api/ecosystem-tools.md) can be used.
Sub-accounts can be created and managed in the Truvera Workspace. Sub-accounts menu is located in the Team settings.
You can create new sub-accounts, edit and delete them from this menu. For any other operation related to the sub-account (creating a DID, issuing credential etc.) you will need to take over that sub-account and do the actions in the account. You can take over the subaccount and use it by clicking on it a message will be displayed that the account is being changed and you will see a new account on the profile menu on the top of the screen.
To come back to the main account you need to click on the profile menu and select Back to main 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 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://docs.truvera.io/truvera-workspace/team-management/sub-accounts.md?ask=&goal=
```
`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.