Skip to main content
Liquid tags are the tenant isolation layer for embeds. You define the tag names in Vizkraft; your backend supplies values at session mint. See Security for the full model. Open app.vizkraft.com → dashboard → Embed → Liquid tags / Coverage.

​
Add liquid tags

  1. Choose a slug (e.g. department_id)—this is the key your backend sends in liquid.
  2. Map it to a table column type (numeric, text, date, datetime).
  3. Mark Required (mandatory) for hard isolation, or leave optional if partners may omit it.
  4. Save.
Optional tags that are omitted at mint leave that dimension unscoped. Prefer mandatory for true multi-tenant products.

​
AI suggestions

On Liquid (and on Coverage when there is a gap), Vizkraft can suggest tags from schema—including one-hop foreign-key joins. Suggestions are scored; you still confirm before they apply at runtime.

​
Coverage by chart

Coverage tab Each chart shows:
  • Covered — at least one confirmed mapping for a liquid tag
  • Not covered — no confirmed mapping
  • Mapping kind: Direct (column on a table in the SQL) or Via FK (join path)
Confirm suggestions carefully. A wrong “direct” table (for example mapping controls charts to audit_findings.department_id) breaks queries at runtime.

​
Uncovered charts

By default, charts without confirmed mappings are hidden in the embed. You can allow them under Viewer options—only when you accept that those tiles are not liquid-scoped.

​
Runtime behavior