> 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/cregis-wallet-guide/zh-tw/resources/faq/team_account/ru-he-jie-san-tuan-dui.md).
# 如何解散團隊？
## **解散團隊的條件**
要解散團隊，請確保賬戶餘額正好為$0。無需移除團隊成員或協作信息。
## 解散團隊後會發生什麼事
完成解散團隊後，成員資訊、分片資訊、協作資訊都將被完全刪除清空。產生的區塊鏈位址將保留，因為這是區塊鏈技術的特性決定的。
## 操作指引
如果您是該團隊的創建者，透過以下指引，即可找到解散團隊的操作入口：
---
# 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/cregis-wallet-guide/zh-tw/resources/faq/team_account/ru-he-jie-san-tuan-dui.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.
