Skip to content

33. Search & Studio Database

Search and Studio Database help operators find and bulk-manage Klariton content across the organization.

Use the Studio search palette to find:

  • BIQs,
  • products,
  • touchpoints,
  • materials,
  • personas.

The search is organization-scoped. It does not return entries from another organization.

Search supports:

  • grouped results by type,
  • type facets,
  • keyboard navigation,
  • direct deep links,
  • short result snippets,
  • status labels.

Typical shortcuts:

  • arrow keys to move through results,
  • Enter to open,
  • Esc to close.
TypeWhat opens
BIQCuration view focused on the BIQ.
ProductProduct library or product focus.
TouchpointTouchpoint detail.
MaterialMaterial detail.
PersonaPersona detail.

If a type has more matches than the palette shows, open the Studio Database view for the full table.

The Studio Database is a table view for the same core entities.

It supports:

  • entity tabs with counts,
  • search filter,
  • status filter where applicable,
  • product filter for BIQs,
  • server-side pagination,
  • saved browser-local views,
  • row selection,
  • bulk action bar.

Saved views are stored locally in the browser. They are useful for recurring filters, but they are not shared team-wide.

Common status buckets include:

  • BIQ: Live, In review, Draft,
  • Touchpoint: Active, Inactive,
  • Material: Processed, Processing.

Products and personas may not have a status pill.

Available actions depend on entity type and role.

BIQs:

  • publish,
  • move to draft,
  • delete,
  • run SafeGuard,
  • re-translate where Translation Management is enabled later.

Touchpoints:

  • activate,
  • deactivate,
  • delete.

Products and personas:

  • delete where supported.

Materials:

  • bulk action support can be limited; use material detail actions for reparse or diagnostics.

Bulk delete uses trash/soft-delete behavior where supported. Confirm before deleting.

Re-translate from Database belongs to the later Translation Management release. When enabled, selected BIQs can be re-translated into configured target locales.

The flow is:

  1. Select BIQs.
  2. Choose Re-translate.
  3. Review the cost estimate.
  4. Confirm.
  5. Monitor translation jobs in Translation Manager.

For selected BIQs, the database can run a SafeGuard drift scan. This is useful after product changes, material refreshes or bulk publication.

SafeGuard creates findings rather than silently changing BIQs.

Read-only users can browse the database. Bulk actions require Owner or Admin.

  • Use search for quick navigation.
  • Use database filters for operational batches.
  • Save local views for recurring review work.
  • Run SafeGuard before bulk-publishing many BIQs.
  • When Translation Management is released, re-translate after source edits or SafeGuard corrections.
  • Avoid bulk deletion unless you understand downstream embeds and touchpoints.