Dashboards
What a dashboard is made of, and how one gets built.
Contents
What is a dashboard?
A dashboard is a grid of widgets that draw from your connected data and refresh on one schedule. You build it by asking. Charts start as previews in a chat, you press Add to dashboard on the ones you want, and you ask for changes from there.
What is on a dashboard?
| Part | What it is |
|---|---|
| Widgets | The charts, tables, KPIs, files and text on the grid. See Widgets |
| Parameters | The filters and date ranges every widget can read. See Parameters |
| Schedule | How often the data behind the widgets is fetched again. See Refresh |
| Context | A written summary of the dashboard, kept current for the assistant and your agent |
| Owner | One person, whose connections the scheduled refreshes run on |
What does each reader see?
Each widget has one published set of data. It is what everyone sees when they open the dashboard at its default filters, and what the public view and embeds show. A scheduled refresh replaces it for everyone, and so can a refresh by hand (Refresh says whose).
Anything else a reader does gives them their own view. Changing a filter, refreshing without the right to publish, or loading charts whose data has expired runs the widgets on that reader's own connections. The result shows to that reader alone. It is never saved and never changes what anyone else sees. See Parameters for filters.
How are widgets laid out?
Widgets sit on a 12-column grid. The grid has no drag handles and no resize corners. Position, size and styling are set by asking the built-in assistant on the dashboard, or your agent:
Put the revenue chart top left, full width, and make it shorter.
Widgets slide upward to fill any empty cells, so a gap cannot be left on purpose. Ask for a spacer instead (Widgets).
How does a dashboard look on a phone?
Narrower screens restack the grid. A phone shows a single column, and a tablet pairs small widgets two to a row. Widgets stack in desktop reading order, top to bottom and then left to right.
Reading order can split widgets that belong together, such as a column of KPIs beside its chart. Ask for a stack order to keep them together.
Warning
Every widget with a stack order sorts ahead of every widget without one. Setting it on one group moves that group to the top of the phone layout, so order the whole dashboard if you order any of it.
What is a dashboard's context?
Every dashboard carries a written summary of itself. It holds a short description, the audience, the key uses, caveats, starter questions, and a plain-language reading of each widget. Vistazo rewrites it a few minutes after the dashboard changes.
The built-in assistant reads this summary on the dashboard, so it can answer questions about a chart it did not build. Your agent reads it too, rather than every chart's raw configuration. Read it under Settings → Context. A workspace admin can also regenerate it there.
Who owns a dashboard?
A dashboard has exactly one owner. Scheduled refreshes run as the owner, on the owner's data connections. An editor can change the schedule or rewire a widget without lending the dashboard their own connections.
If the owner leaves the workspace, the schedule stops and the Schedule card says why. To hand the dashboard to someone else, open Settings → Sharing and pick Owner on a collaborator's row. Giving the dashboard an owner turns its schedule back on. See How sharing works.
How do you archive a dashboard?
Archive a dashboard from the Archive card at the bottom of Settings → General. An archived dashboard stops refreshing and disappears from lists and from agent tools. Nothing is deleted, and Restore dashboard on the same card brings it back.
A dashboard holds up to 100 live widgets. See Limits.