> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/sandbox-management/sandboxes/deleting-a-sandbox.md).
# Deleting a Sandbox
##  Overview
This article explains how to delete a sandbox in Sandbox Management. Deleting a sandbox deletes it in Salesforce too, so it no longer appears in Salesforce Setup on the **Sandboxes** page.
Deleting a sandbox doesn't delete its organization in Global Settings. The organization stays in your tenant so that you keep any data stored for it, such as Audit & Compliance audit logs and Backup & Archive backups. If you no longer need this data, you can delete the organization from Global Settings after you delete the sandbox.
{% hint style="warning" %}
#### Deleting Can't Be Undone
Deleting a sandbox permanently deletes the Salesforce sandbox and everything in it. Before you delete a sandbox, deploy any changes you want to keep to production.
{% endhint %}
## Deleting a Sandbox in Sandbox Management
{% stepper %}
{% step %}
### Open the Sandbox
1. Click **Sandboxes** from the left sidebar menu.
2. Click the sandbox you want to delete.
3. The sandbox's details open.
{% hint style="info" %}
#### Refresh Interval
You can delete a sandbox only after its **Next available** time has passed. The refresh interval applies to deleting a sandbox as well as refreshing it: for a Developer sandbox, 24 hours after it was created or last refreshed. If you try to delete the sandbox earlier, Sandbox Management shows an error and the sandbox isn't deleted.
{% endhint %}
{% endstep %}
{% step %}
### Delete the Sandbox
1. Click **More**.
2. Click **Delete**.
3. Enter the sandbox's name to confirm.
4. Click **Yes, delete**.
5. The sandbox no longer appears in the **Sandboxes** list.
{% endstep %}
{% endstepper %}
## Deleting the Organization in Global Settings
If you no longer need the data stored for the sandbox's organization, delete the organization in Global Settings.
{% hint style="warning" %}
#### Deleting the Organization Deletes Its Data
Deleting the organization permanently deletes all data stored for it in your tenant, such as Audit & Compliance audit logs and Backup & Archive backups. This can't be undone.
{% endhint %}
{% stepper %}
{% step %}
### Open Global Settings
1. Click the **App Switcher** at the top of the left sidebar menu.
2. Click **Global Settings**.
{% endstep %}
{% step %}
### Delete the Organization
1. Click **Organizations** from the left sidebar menu.
2. Click the three vertical dots at the right end of the sandbox's row.
3. Click **Delete Organization**.
4. Enter the organization's name to confirm.
5. Click **Delete**.
6. The organization no longer appears on the **Organizations** page.
{% hint style="info" %}
#### Learn More About Deleting an Organization
To learn more about deleting an organization in Global Settings, see the following article.
* [Deleting an Organization](/global-settings/environment/organizations/deleting-an-organization.md)
{% endhint %}
{% endstep %}
{% endstepper %}
---
# 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://docs.flosum.com/sandbox-management/sandboxes/deleting-a-sandbox.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.
