Skip to main content
Archiving hides a workspace and its nested workspaces from active lists. It also starts the archive of the artifacts, projects, and repositories they contain. The archived workspace remains readable to identities with access.

Before you begin

  • You need archive permission on the selected workspace and every affected workspace in its subtree.
  • Personal workspaces and the organization root cannot be archived.
  • The app requires the selected workspace to have no artifacts before enabling Archive workspace. Move anything you want to keep out of its descendants too.
  • Check the whole subtree with its administrators. A live descendant you cannot read prevents the archive.
The app has no restore control. Move retained work first and plan this as retirement. A successful workspace archive does not establish that every contained artifact has finished archiving: an artifact’s own checks can refuse that part of the operation.
1

Open danger zone

Open Settings, select the workspace under Workspaces, select General, then find Danger zone.
2

Archive workspace

Select Archive workspace. Review the workspace and subtree named in the confirmation, then select Archive.If the action is disabled, read its explanation. The selected workspace may still contain artifacts, or your identity may lack permission. See Workspace archive blocked.
3

Verify archive

Confirm the affected workspaces leave active lists. Saved links remain available to identities with read access.Atlan renames each archived workspace with an ID suffix to free its old name. This also changes that workspace’s marketplace plugin path. The content archive runs separately; check its result before concluding all records have retired.

If descendant or artifact blocks operation

A workspace_subtree_unseen conflict means a live descendant was not visible to the archiving identity. No archive is applied in that case. Ask that descendant’s administrators to archive it first, then retry the parent. If the workspace archives but some content refuses, resolve the reported refusal before retrying. The API’s archive response includes a cascade run ID for status inspection through the action-run API. Re-archiving an already archived workspace can retry the content cascade; it does not restore the workspace. To keep a workspace active while changing who can reach it, manage workspace access instead.