Skip to content

Dashboards

A Native Dashboard keeps the Cards you want to come back to. Unlike a Card in a Conversation, a Card on a Dashboard queries its Data Source again whenever you refresh it, so it shows current data.

Below a Card, select + Dashboard, then New Dashboard, or one of your Dashboards listed below it. The Web App puts a copy of the Card on that Dashboard, below everything already there, and opens it. The copy takes the Card’s chart type, its query and the settings you changed. It stays apart from its Conversation: deleting the Conversation leaves the Dashboard as it is.

Only a Card from a Data Source can go on a Dashboard, because only its query can be repeated.

A Dashboard is a file in your Personal Drive, in the folder Dashboards/, named after its title, such as Revenue by region.dashboard.json. Its earlier states are its File Versions, and deleting the file deletes the Dashboard.

Select Dashboards above your Conversations. The list shows every Dashboard file in your Personal Drive, wherever it is, by title. Select one to open it.

On a Dashboard you can change, its Cards and texts sit on a grid of 12 columns:

  • An element’s title and its controls share one row: the handle, then refresh, the chart’s Settings, Fullscreen and the … menu. A title too long for the row is cut short; point at it to read all of it.
  • Move an element by dragging its handle, or focus the handle and press the arrows on your keyboard. While you drag, a dashed outline shows where it will land, and the other elements make way for it.
  • Resize it by dragging the grip in its bottom right corner, or focus the grip and press the arrows on your keyboard. A Card is never lower than Small, so its chart always has room; a text can be one row.
  • The … menu sets an element’s Width (Full, Half or Third) and Height (Small, Medium or Large) with one click, moves it earlier or later in reading order, edits a text, and removes the element from the Dashboard.
  • When you move or resize an element, the others make room: those in its way move down, and gaps close upwards.
  • Add text adds a text in Markdown below everything, such as a heading or a note. Edit it from its … menu.
  • The pencil next to a title renames the Dashboard or a Card.
  • A Card’s chart fills the Card. Below it you change its chart type and its options; its Settings (colours, legend and axis titles) are among the Card’s controls, as on a Card in a Conversation. Fullscreen opens the Card over the whole window; press Escape to close it.

Every change shows at once and is saved to the Dashboard for everyone who opens it. If a colleague changes the same Dashboard at the same time, both changes are kept, as long as you change different things; on the same thing, the later change wins. If you change an element that someone else removed meanwhile, the page says so and shows the Dashboard as it is now.

If you can only read a Dashboard, you can’t arrange it. You can still change a Card’s options and settings, for yourself: they aren’t saved, and others don’t see them. The chart type stays as it is.

On a phone, the elements stack in one column.

Ask the agent to build or change a Dashboard

Section titled “Ask the agent to build or change a Dashboard”

In any Conversation, ask the agent for a Dashboard, such as “Put revenue by region and orders per month on a Dashboard”. It queries your Data Sources and creates the Dashboard in Dashboards/ of your Personal Drive, with its Cards and texts. Ask it to change a Dashboard you have, by its title, and it adds, changes, moves or removes Cards and texts on it. It finds your Dashboards in your Personal Drive, wherever they are. The page shows a Dashboard’s title above its elements, so the agent doesn’t repeat it as a text.

Each time, the agent’s answer shows a card with what it did. Expanded, it lists what the Dashboard holds; Open takes you to the Dashboard. Each change it makes is a File Version of the Dashboard, so you can restore an earlier state. The agent doesn’t ask before it changes a Dashboard.

  • The agent can’t share a Dashboard: that stays your decision.
  • If a query fails or a chart doesn’t fit its result, the agent changes nothing and says why.
  • A Card you can’t see is locked for the agent too: it sees neither its query nor its data.

On a Dashboard, Ask the agent opens a side panel with a Conversation about that Dashboard. Ask about what you see, such as “Which region grew most?”, or ask for a change, such as “Add revenue per month below”. The agent knows which Dashboard you have open; once it changed it, the Dashboard shows the change. On a phone the panel covers the Dashboard, and × brings it back.

The panel’s Conversation is yours alone, like any other: the agent works with your access, and it is in your list of Conversations once you sent a message. When you open the panel again, even days later, it continues your last Conversation about that Dashboard. Delete that Conversation, and the next time the panel starts a new one.

If you can only read a Dashboard, the panel says so. The agent explains and analyses it but doesn’t change it; when you want something changed, it offers to make you a copy in your Personal Drive, which you and the agent can change.

If your Tenant has Metabase and you connected it, the agent can build a dashboard there too, with Metabase’s own tools. When both fit what you ask for, it follows what you said, or your Memory if it holds a preference, such as “Build my dashboards in Metabase”. Otherwise it asks you which you want, or chooses itself when one clearly fits better, and says which.

A Native Dashboard can’t be moved to Metabase as it is. Ask the agent to move one, and it says so, then rebuilds it in Metabase Card by Card. Changes in Metabase ask for your Approval first, as every Metabase tool that changes something does.

Each Card shows the time of its result. A Card queries its Data Source again only when someone refreshes it:

  • Refresh all refreshes every Card of the Dashboard.
  • The refresh button of a Card refreshes that Card alone.

While a Card refreshes, a placeholder shaped like a chart takes its place. Up to six Cards refresh at a time, and each may take up to 60 seconds. A Card that fails, or takes longer, shows its own error; the other Cards keep theirs.

A new Dashboard’s Cards have no result yet, so they refresh the first time you open it.

The result of a refresh is kept for the Dashboard: everyone who opens it later and has access to the Card’s Data Source sees that result, with its time, until someone refreshes it again. A refresh uses your access.

  • If you have no access to a Card’s Data Source, the Card is locked: it shows its title and the name of its Data Source, but no data and no query.
  • If its Data Source was deleted, the Card says so and can’t be refreshed any more.

A Dashboard file can be changed by code, such as code the agent runs in the Sandbox. When you open a file that is no longer a valid Dashboard, the page says what is wrong with it instead of showing the Dashboard. Restore an earlier File Version to get it back.