> 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/workspaces-faq/deleting-workspace.md).

# Deleting a workspace

What happens to your drives, files, plan, and account when you delete a workspace.

Deleting a workspace permanently deletes every drive and asset in it, and cancels the workspace's plan.

{% hint style="danger" %}
Deletion is immediate and can't be undone. All drives and uploaded assets in the workspace are deleted as soon as you confirm.
{% endhint %}

### What happens when you delete a workspace

* **Drives and files:** every drive in the workspace, and every asset uploaded to it, is deleted right away.
* **Your plan:** the workspace's plan is canceled. Any time left on a monthly or annual plan isn't refunded. If you're starting a new workspace, contact us and we'll move your existing plan over to it.
* **Your Shade account:** your account isn't deleted. You can still sign in, and you keep access to any other workspaces you belong to.

See [Can I get a refund?](https://academy.shade.inc/help-center/billing/can-i-get-a-refund.md) for Shade's refund policy.


---

# 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/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.
