> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/help-center/help-center-zh/workspaces-faq/deleting-workspace.md).

# 删除工作区

删除工作区后，您的驱动器、文件、套餐和账户会怎样。

删除工作区会永久删除其中的所有驱动器和资源，并取消该工作区的订阅方案。

{% hint style="danger" %}
删除会立即生效且无法撤销。确认后，工作区中的所有驱动器和已上传资源都会立刻删除。
{% endhint %}

### 删除工作区后会发生什么

* **驱动器和文件：** 工作区中的每个驱动器以及上传到其中的每个资源都会立即删除。
* **你的订阅方案：** 该工作区的订阅方案将被取消。按月或按年方案剩余的使用时间不予退款。如果你要创建一个新工作区，请联系我们，我们会将你现有的方案迁移过去。
* **你的 Shade 账号：** 你的账号不会被删除。你仍然可以登录，并且仍可访问你所属的其他任何工作区。

参见 [我可以获得退款吗？](/help-center/help-center-zh/ji-fei/ke-yi-tui-kuan-ma.md) 查看 Shade 的退款政策。


---

# 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://academy.shade.inc/help-center/help-center-zh/workspaces-faq/deleting-workspace.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.