> ## Documentation Index
> Fetch the complete documentation index at: https://learn.biq.li/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete a workspace

> Permanently remove a workspace and its associated data.

Deleting a workspace is a destructive administrative action. It affects the workspace's resources, integrations, member access, API keys, and workspace-specific configuration.

Before deletion, export anything you must retain, remove live integrations, replace published URLs, and settle any billing requirements shown in the dashboard.

Only an authorized owner can confirm deletion. Read the confirmation screen carefully because deleted workspace data might not be recoverable.

## Prepare a deletion checklist

* Export links and reports that must be retained.
* Replace live short URLs, Biolinks, and QR placements.
* Review custom-domain DNS and attachments in other workspaces.
* Disconnect external integrations and revoke workspace API keys.
* Notify members and transfer anything that belongs elsewhere.
* Review the active subscription, invoices, and confirmation consequences.

## Confirm the correct target

Workspace deletion has a much wider scope than deleting one link. Verify the
workspace name, slug, owner, and billing context before entering the required
confirmation.

After deletion, previously distributed URLs can stop working and members lose
access. Removing DNS or provider integrations is a separate external action and
should be completed only for the exact workspace and hostname involved.

Contact support before confirming if the workspace is part of an ownership,
billing, legal-retention, or security incident.

## Frequently asked questions

### Is deleting a workspace the same as canceling its plan?

No. They are separate actions with different resource and billing effects.

### Can I keep a custom domain after deletion?

Review whether it is attached elsewhere before deleting. DNS ownership remains
external, but the deleted workspace attachment and resources do not.