Dashboards
Metrics (saved filters over datasets), grid dashboards and KPI reports — built by hand or by an AI agent
In short
How it all fits together
The pieces in the order they build on each other: dataset, metric, component, then dashboards, goal lists and reports
What is a dataset?
A named, filterable table of data: the layer between a data source and everything built on it
What is a metric?
A saved filter over a dataset, rolled up to one number: the reusable unit behind every card, goal and report row
What is a component?
A saved card: a dataset filtered for it, or a metric for a single number, drawn by one design, built once and placed on any number of dashboards
What is a dashboard?
A grid of cards over your metrics: reading one, building one, and who can see it
What is a goal list?
Key numbers against their targets, read down in a meeting: on target, at risk or missed
What is a report?
A table of metrics across periods that sorts, drills into its rows, prints and downloads
What is a playlist?
Dashboards and goal lists one after another: paged through in a meeting, or rotating on a wall screen
Weeks, captures and history
How a goal list keeps its numbers as they stood when a week, day or month ended
Guides
Dashboards
Metrics, dashboards and reports: what each is, editing a layout, the period bar, sharing
Building a metric
The metric builder: datasets, AND/OR filters, periods, aggregations, thresholds, and the stored JSON
Goals
Key numbers against their targets, in sections: on target, at risk or missed, for reading down in a meeting
Playlists
Dashboards in a sequence: page through them like slides, or rotate them on a wall screen
Agents and the API
Have an AI agent build dashboards over MCP or REST — the tools, the loop, and the access rules