Skip to main content

Archive and restore assets

Assets now have a full archive lifecycle. Archiving removes an asset from the active knowledge base without deleting it permanently: the asset keeps its identifier, properties, history, access domains, and references until you restore it or delete it for good.

Archive instead of deleting

In each inventory, the Delete action now moves an asset to the archives rather than erasing it. You can archive a single asset from its row menu or edit dialog, or select several rows and archive them in one transactional operation. Archiving deactivates the asset's relationships but keeps them stored for a later restoration, and it records the archive date in the asset history.

Archiving requires the delete_asset right on the asset's type and access domains.

Browse and restore

Each asset-type inventory gains a View archives toggle. The archived list keeps your usual view tools: search, filters, sort, grouping, visible fields, and display modes. It also adds an Archived on column. Archived assets are read-only; open the preview or 360 page to review their information, relationships, rights, history, and comments.

Restore reactivates the same asset with all its data, and brings back relationships once both endpoints are active again. Restoration requires edit_asset.

Permanent deletion, when you really mean it

Permanent deletion is a separate, irreversible action available only after an asset is archived. It removes the asset, its history, comments, and remaining relationships, and breaks any share links and dashboard widgets pointing at it.

What happens to visualizations

Archiving preserves references so a restored asset returns to its previous contexts. On diagrams, the node stays in place and is shown as inactive, with a grey striped fill. It returns to its normal look once you restore the asset. Dashboard widgets report the asset as removed, and charts and nested maps stop counting it.

Read the full Archive and restore assets documentation.

Why this matters

Removal is rarely final. The archive lifecycle lets teams retire assets from day-to-day work without losing their history or their place in diagrams, dashboards, and flows. Teams can bring them back intact when needed. Permanent deletion stays a deliberate, separate step.