Dashboards

A Dashboard is a page of live panels. It’s what you build when multiple answers belong on one page, updated continuously, shown to multiple people.

Tablize Dashboards are different from the BI tool you’ve used before. You don’t open a canvas and drag widgets onto it. You describe what you want, the Agent builds the panels. You refine by asking.

Creating a Dashboard

Three entry points:

• From an answer. Click ＋ Build Dashboard in the Keep bar. The Agent uses the answer as the seed panel.
• From scratch. Sidebar → Dashboards → + New. Describe the dashboard: “Ops dashboard for cold chain — current temps, alerts, camera feed.” The Agent builds a draft.
• From a template. Sidebar → Templates → pick one → fork into your workspace. Good for common patterns: signup funnel, revenue breakdown, support triage.

First draft appears in Split view. Edit by asking:

• “Add a panel showing refund rate by day for the last 30 days.”
• “Move the KPIs to the top.”
• “Replace the bar chart with a line chart.”
• “Use the synthwave theme.”

Each change is a single Agent turn. The Dashboard updates live.

Anatomy of a Dashboard

• Panels — individual visualizations (KPI, chart, table, map, embed).
• Layout — grid of panels, drag-and-drop to reorder or resize (or just ask the Agent).
• Data Contract — each panel has a declared query. The backend serves the query’s results directly from Postgres — millisecond response, no Agent in the loop.
• Refresh — per-panel refresh rate. Default varies by data source (5s for IoT, 1m for DB, 5m for integrations).
• Theme — one of 11 themes (see below).

Panels are composable. A single Dashboard can mix a Postgres KPI, a Shopify integration table, an MQTT live gauge, and an embedded Watch history — all on one page.

Themes

Dashboards (and Apps) support 11 themes. All are driven by CSS variables; switching is instant and affects every panel.

Theme	Character
monochrome (default)	Black / white / gold — matches Tablize brand.
arctic	Pale blues, high contrast.
glass	Glassmorphism — frosted cards, soft gradients.
brutal	Raw borders, no shadows, high density.
aurora	Purple-green gradients, ambient glow.
synthwave	Neon on black — good for dark-room ops.
terminal	Green monospace on black. Nostalgic.
corporate	Conventional blue SaaS, if you must.
midnight	Very dark, minimal color. Easy on night-shift eyes.
gradient	Bold colorful gradients.
neonmint	Mint on near-black.

Ask the Agent: “use the synthwave theme.” Or pick from the theme dropdown in the Dashboard toolbar.

Data freshness

Dashboards are pull-based. Each panel has a refresh_every: 5s / 1m / 5m / 1h / 1d setting. On each refresh:

1. Panel’s query runs.
2. Result is diffed against the previous render.
3. Only changed parts animate.

For IoT panels, Tablize can also do push (live-stream MQTT topics directly to the panel). Push is preferred for sub-second updates.

Some rules of thumb:

• KPIs — 1 minute is usually fine.
• Charts over DB data — 5 minutes.
• Integration-backed panels — match the integration’s sync cadence (5 min for Shopify, 1 hour for Ads).
• IoT gauges — 5 seconds or push.
• Camera frames — the frame sample rate on the asset.

Faster refresh = more compute. Dashboards under heavy refresh can affect your token budget on Plus; they don’t on Pro or Max (compute is included).

Sharing and embedding

Three modes:

• Private — workspace members only.
• Team link — members plus Viewer seats.
• Public — anyone with the link. No login.

Public dashboards support oEmbed:

https://app.tablize.com/d/<id>

Paste that URL in Notion, Confluence, or Slack and you get a live embed. Most Markdown-based tools render it. For tools that don’t, use the iframe:

<iframe src="https://app.tablize.com/d/<id>/embed" width="100%" height="600"></iframe>

The embed respects your current theme. Dashboards embedded in Notion adopt their parent’s light/dark mode if you pick auto theme.

Viewer seats

Non-Creator users who read Dashboards use Viewer seats ($5/month). A Viewer can:

• Open any Dashboard shared with them.
• Click panel drill-downs (see below).
• Export panel data to CSV.
• Subscribe to a Dashboard (receive a daily screenshot by email).

A Viewer can’t:

• Chat with the Agent.
• Edit a Dashboard.
• See a panel’s underlying query unless the Creator exposes it.

See Workspaces & roles for seat management.

Drill-downs

Click any KPI or data point in a Dashboard to see the underlying rows. Creators also get:

• “Explain this” — opens a chat session with the panel as context.
• “Edit the query” — drops into the Data Contract for that panel.

Viewers only see drill-down tables, not queries.

Dashboards vs Apps

	Dashboard	App
Purpose	Display data	Do things with data
User actions	Read, drill, export	CRUD — add/edit/delete
Latency	Millisecond queries	Millisecond queries
Data Contract	Read-only queries	Read-write endpoints
Typical maker	Ops lead, founder	Founder, operations lead

Rule of thumb: if teammates are reading, build a Dashboard. If teammates are writing back to the data, build an App.

Common gotchas

• Panel shows “No data” after a schema change. The Data Contract references a column that no longer exists. Click the panel → Repair — the Agent proposes a fix.
• Public link loads slowly. Your refresh rate is aggressive. Stepping it down one tier usually helps.
• Embed in Notion doesn’t render. Some Notion page types block iframes — use the oembed URL instead.
• Dashboard looks great in desktop, cramped on phone. Ask the Agent: “make this mobile-friendly.” It rearranges panels into a single column.

Next steps

• Apps — when you need the data to be editable.
• Reports — when the right shape is a narration rather than a grid.
• The Keep loop — the other three shapes an answer can take.