Skip to main content

Build your first card and dashboard

With a dataset saved, you can turn its rows into a card -- a single chart, table, or KPI -- and compose cards into a dashboard your team can open.

Create a card​

Open My reports → Cards and start a new card. A card gets its data one of two ways:

  • From a dataset -- pick any saved dataset and shape its cached rows. Available from the Explorer tier (T2) up.
  • From direct SQL -- the card carries its own query. Requires the Builder tier (T4) or above.

For a first card, bind to the dataset you just created, then:

  1. Pick a chart kind. The library runs from the essentials -- KPI, table, line, bar, area, pie, scatter, donut -- to specialised kinds like heatmap, funnel, waterfall, sankey, gauge, treemap, and radar. See the chart library for the full set.
  2. Shape the data with a transform. Filter rows, group by a column, aggregate (sum, average, min, max, count), sort, and limit. Transforms run in the browser against the dataset's cached result, so tweaking them costs nothing at the warehouse. Leave the transform empty to pass the rows straight through.
  3. Name the card and save.

The editor previews the chart live as you adjust the transform and the chart's options. More detail in Cards.

Compose a dashboard​

Open My reports → Dashboards and create a new dashboard. You choose a layout mode at creation:

  • Grid (the default) -- a responsive 12-column layout that stacks on mobile.
  • Canvas -- a fixed-size page with pixel-precise placement, available with the Designer tier (T5) on the Team plan. See Canvas.

In the editor, insert your saved cards and any text headings you want, arrange and resize them, and save. The same card can appear on several dashboards -- they all share the dataset's cache. See Dashboards for filters, themes, and the rest.

Where it lands​

Every new card and dashboard starts in the playpen -- the working area of the library -- and moves to the certified library only when it is certified, so viewers can always tell trusted content from work in progress (see Certification and peer review).

Good to know​

  • Viewing a dashboard never runs SQL for viewers; they read cached results.
  • Anyone with build rights sees an Edit button on the dashboard view, jumping straight back into the editor.

Next: invite your team so someone can actually see it.