---
title: Delete resources
description: Permanently delete a workspace, site or survey, or preserve its data by disabling or archiving instead.
url: https://docs.userreason.com/get-started/delete-resources/
updated: 2026-10-16
---

# Delete resources

Permanent deletion removes a resource and its associated data. Use archive or disable when you want to stop delivery and keep historical results. You do not need to archive a resource before deleting it.

| Resource | Permanent deletion removes |
| - | - |
| Survey | Its draft, published versions, responses and delivery history. Shared survey definitions still used by another survey are retained. |
| Site | Its surveys, audiences, event definitions, stored events, visitors, responses and settings. Other sites remain. |
| Workspace | Its sites and their associated data, memberships and workspace-specific access grants. Your user account and other workspaces remain. |

In the dashboard, use **Delete permanently** in workspace settings, site settings or a survey's action menu. Review the affected record counts and type the exact resource name to confirm. Large counts display `10000+` instead of counting an entire event stream. If another survey or saved audience references the survey, remove that reference before confirming.

## Permissions

Owners and admins can delete resources. CLI and MCP connections also need the separate `resource:delete` permission; an existing connection never gains it automatically. Run `userreason access --open` to review access when needed. A request to archive or disable a resource does not authorize permanent deletion.

## What happens after confirmation

Delivery stops immediately. Cleanup runs in bounded background batches, including removing cached configurations and copies of deleted survey text from stored snapshots. Other surveys' versions and responses remain intact. The deletion receipt reports progress and automatically retried cleanup failures. You may close the dialog while cleanup continues.

Deletion is irreversible. A minimal receipt retains resource IDs, requester identity, timestamps and cleanup progress so retries and status checks work after the resource is gone; it does not retain the deleted questions or answers. Provider backups expire separately according to their retention policies, rather than being erased synchronously with an individual resource.

## CLI and MCP

The [CLI](https://docs.userreason.com/cli/index.md#permanent-deletion) provides previews, explicit confirmation and status. With MCP, use `deletion_preview`, then `deletion_request` with the reviewed token, name, revision and a stable request ID. `deletion_status` reads your receipt. Each interface uses the same permission checks and deletion process.