What "live" means
When you build an interactive dashboard in Chat, it can be wired directly to the client's actual data rather than filled with pasted-in numbers. Dashboards wired that way are eligible to go live: you'll see a lightning-bolt LIVE indicator on the artifact in chat. That badge is earned, not decorative — it only appears when the dashboard's numbers are genuinely bound to real data sources. A mockup with typed-in figures can't go live, and if you try, Omega tells you why it isn't eligible instead of quietly faking it.
Making a dashboard live
In Chat, ask for the dashboard you want — a KPI overview, a pacing view, a channel breakdown.
On the artifact, look for the lightning bolt. Click it to promote the dashboard to the Workbench.
It now lives in the Workbench as a live document, with a Live badge on its card.
How refresh works
Every time you open a live dashboard, it re-pulls its data:
An as-of badge shows exactly how fresh the numbers are, so nobody presents stale figures unknowingly.
While a refresh runs you keep seeing the current version — the page never goes blank waiting on data.
If the numbers actually moved, the dashboard re-renders and saves as a new version; earlier versions stay in history. If nothing changed, nothing churns.
There's a Refresh button when you want to force a pull without reopening.
If a refresh fails, the last good version keeps rendering — a data hiccup never costs you the dashboard.
Freezing for a meeting
Sometimes you want a snapshot — you've rehearsed a client call against specific numbers and don't want them shifting as you present. Use Freeze on the dashboard to pin the current version; it stops refreshing until you unfreeze it. Freeze before the call, unfreeze after.
Tip: Live dashboards shine for anything you open repeatedly — a weekly pacing check, a channel health view you glance at before standup. Build it once in Chat, promote it, and stop regenerating the same report every week.
Note: Live dashboards are for the internal team. For client-facing HTML work, publish through the Artifact Portal instead — see "Client-ready deliverables."