> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/2.-transaction-and-account/space.md).
# Team Space and Personal Space
Cregis account is automatically set up with a personal account. Users can use this personal account to create team accounts. In a team account, the team owner can authorize team members to create wallets. The same wallet can have multiple members added to jointly use and manage it.
## What is the difference between Team Space and Personal Space?
The primary difference between Team Space and Personal Space lies in the available features. In Team Space, additional tools such as dashboards, risk management features, and other advanced functionalities are unlocked. These features allow users to more effectively manage their crypto assets in a collaborative environment, offering enhanced control and oversight compared to Personal Space.
## How to switch the space?
You can refer to the image below and click the top left corner to switch between spaces. Once clicked, you’ll be able to select either the Team Space or Personal Space.
---
# 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://support.cregis.com/2.-transaction-and-account/space.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.
