Skip to content

21. Structure, Folders, Layers & Trash

Klariton organizes public and internal experiences in a content tree. Layers are the top-level areas, folders organize touchpoints inside a layer, and Trash keeps deleted content recoverable for a limited time.

A layer is a high-level container for touchpoints.

Common layer templates include:

TemplateUse it for
ShopTouchpoints on a shop or website.
BackendInternal touchpoints for your team.
Custom LayerA freely defined area.

Layer settings include a name and a URL. The URL should be the place where the Klariton widget is expected to run.

Folders organize touchpoints inside a layer. Use folders when a layer has multiple use cases, product groups, markets, or teams.

Folder actions include:

  • create,
  • rename,
  • delete,
  • move by drag and drop,
  • add touchpoints,
  • add nested folders.

When deleting a folder, Klariton can either move touchpoints up to the layer root or move affected content to Trash, depending on the selected delete mode.

The tree lets you move folders and touchpoints. Moving changes organization and navigation, not the public answer text.

Watch for:

  • name conflicts at the same level,
  • moving a folder into itself,
  • old embed snippets after touchpoint slug changes,
  • deleted touchpoints that are still embedded on a customer site.

Open Trash to restore deleted content. Deleted content is kept for 30 days and can then be permanently removed.

Trash item types include:

  • touchpoint,
  • folder,
  • layer,
  • persona,
  • BIQ.

Restoring returns the item to the organization where it belongs. If the original parent no longer exists, restore behavior can depend on the item type and current tree state.

  • Keep layers aligned with real delivery contexts, such as website, shop, or internal backend.
  • Use folders for product lines, regions, or customer journeys.
  • Avoid changing slugs after production embeds are live.
  • Check Trash before recreating deleted content.
  • After restoring a touchpoint, verify its status, embed snippet, and linked materials.

See also Embedding Touchpoints and Troubleshooting & FAQ.