Docs Developer Site
Developer Docs Content Studio 6.x Actions Delete

Delete

Contents

The Delete action removes content from the active tree. Deleted items are not destroyed — they are moved to the Archive, from which they can later be restored or permanently removed.

There are three ways to invoke Delete:

  • Keyboard shortcut — ⌘ + del on macOS, ctrl + del on Windows/Linux.

  • The Delete button in the toolbar.

  • The Delete entry in the context menu (right-click an item in the Navigator).

A selection is always deleted together with all of its descendants, so the archive preserves the original structure. The dialog lists every item that will be moved.

Delete dialog
Online content (published items) is taken offline immediately when deleted. The item remains in master only until the delete completes, and end users lose access the moment the action is confirmed.

Reference checks

If any item in the selection is referenced by other content that is not being deleted along with it, a warning appears at the top of the dialog and the action button is disabled. The referenced items are marked with a small "link" icon over their content-type icon.

Two links are available:

  • Ignore inbound references — proceed anyway. Referring content will then point at a non-existent item.

  • Show references — open the reference list for each flagged item, so the references can be edited out. Once the references are removed (and saved), the delete dialog refreshes and allows the action.

Permanent deletion

Delete is a soft operation — the content is moved into the Archive and remains recoverable. Permanent deletion happens only from the Archive view, where a separate Delete action physically removes the item from storage. Permanent deletion is not reversible (short of a snapshot restore).

Permanent delete from the Archive dropdown

Delete in layers

Delete behaves specifically when layers are involved:

  • Archiving an item in a parent layer also archives corresponding items in descendant layers that still inherit both its content and location. A descendant with either dimension made local, or with an external reference that prevents archiving, remains in place.

  • Archiving an inherited item directly in a child layer does not affect its parent. The archived copy becomes local and stops receiving inherited changes.

  • Restoring that copy from the layer’s Archive restores it as local content.

  • Permanently deleting an inherited item while its origin still exists in the parent can cause synchronization to create a fresh inherited copy. To keep inherited content out of the active tree, leave it in the Archive instead of permanently deleting it.

See Layers and localization for how this behavior relates to inheritance.

Contents

Contents