Use cases
Dashboards enable you to:- Monitor key metrics – Display critical business indicators that refresh with live data
- Distribute analysis – Package your findings into reports for regular distribution
- Build data tools – Develop specialized applications powered by your semantic layer, or turn the dashboard into an app with its own code
- Present insights – Showcase important discoveries in a polished, accessible format
- Discuss results – Ask questions and agree on answers in comments on the dashboard or on one chart
How it works
In the dashboard builder inside your workbook, select the reports you want to include and arrange them on the canvas alongside other widgets to tell your data story, then publish the dashboard. This gives stakeholders direct access to the insights that matter most, without the complexity of the underlying analysis. Prefer to manage dashboards from source control? You can also apply dashboards, workbooks, and reports to a deployment through the REST API and keep their definitions in Git — see Dashboards as code.Publishing and versions
A workbook holds a single dashboard, which stays a draft until you publish it. Click Publish in the dashboard builder to publish the current draft as a new version — viewers always see the latest published version, never your in-progress edits. Publishing is a workbook-level operation — the same one the as-code flow performs over the API. The button next to Publish reflects the dashboard’s state — click it to open the revision history:v{N}— the published version and your draft match.- Draft — you have unpublished changes.
Revision history
The revision history lists every published version alongside the current draft. Each row shows the version number, when it was published, by whom, and one line on what the version changed. Cube writes that line in each viewer’s language. A few seconds after publishing, AI may replace it with a line that names the change inside a widget, written in the publisher’s language. Older versions may have no line. Select a version to preview it, then Restore to make it your current draft — publish again to make it the live version. The history also lists the revisions of each review: select one to preview it, or click its Open review button to open the review.What viewers see
When someone opens a published dashboard, a version chip in the header shows the live version (e.g.v3). Opening it reveals when that version was published and
a summary of what changed since the previous version — added, updated, or removed
widgets — so viewers can see which version they’re looking at and what changed in
it. (The chip is in-app only; it doesn’t appear on embedded
dashboards.)
Live updates
You don’t have to reload to see a change made somewhere else: by an AI agent connected through the MCP server, by another person, or by you or the Workbook Agent in another browser tab.- In the dashboard builder, a chart added, changed or deleted and a change to the dashboard draft show as soon as they are saved, and a publish updates the button next to Publish. Undo reverts a change that arrived this way as one step.
- On a published dashboard, a new publish shows as soon as it is published; draft changes never reach it. Your control selections, cross-filters, the dynamic controls you added and the tab you chose are kept. One whose control, chart or tab the new version removed is dropped, as reloading the page would drop it.
Full screen
To show a published dashboard in a meeting or on a wall display, open the More actions menu (⋮) at the right end of the dashboard header and choose
Full screen, the first item. The browser goes full screen and the dashboard
fills it: the sidebar, the dashboard header, an open comments, scheduled
refreshes or agent panel, and the floating chat button are hidden. Controls,
tabs and a chart’s Explore keep working.
Press Esc to leave full screen. After you entered from the menu, the
browser’s Back button leaves too, which is the way out on a device with no
Esc key. The dashboard comes back as you left it: your control selections and
tabs are kept, and a panel that was open is open again.
If the browser doesn’t allow full screen, the dashboard still fills the browser
window, without the sidebar, header and panels. Whenever it fills only the
window, that way or from a link, an Esc that closes an
open list or dialog closes only that; press Esc again to leave.
Full screen needs a window at least 920 pixels wide. In a narrower window, such
as on a phone, the header offers no Full screen item and a full-screen
link opens the dashboard as usual, with its sidebar and
header. Narrowing the window below 920 pixels while in full screen brings the
sidebar and header back and takes the browser out of full screen.
Open a dashboard in full screen from a link
Addfullscreen=true to a published dashboard’s address to open it without the
sidebar, header and panels, for example on a TV:
true turns it on, and it combines
with the control and tab parameters,
so a link such as ?fullscreen=true&tg_orders.created_at=week opens with that
granularity picked. The link opens the dashboard in Cube, so the browser showing
it needs to be signed in with access to the dashboard; an embedded
dashboard hides its
header with showDashboardHeader=false instead. Ask the Dashboard
Agent for a link to show the dashboard on a TV, and it
answers with this link; ask it to keep the dashboard refreshing too, and the
link also carries autoRefresh.
Live mode
Live mode keeps a published dashboard current while it is open, for example on a wall display: every few minutes it refreshes the whole dashboard, as Refresh all charts on the dashboard’s freshness leaf does, and also re-runs every Analysis widget that has already run. It runs only in a browser tab that has the dashboard open. Refreshes, deliveries and alerts run on Cube’s servers whether anyone has the dashboard open or not. To offer it to viewers, open the dashboard in the builder, open the options sidebar, and turn on Live mode on the Editing tab, right below Cross-filtering. Set Refresh every (minutes) to a whole number of minutes from 1 to 1440 (one day); it starts at 5. Then publish the dashboard: viewers get the setting with the published version, not with your draft. Turning the switch off keeps the minutes you set, so turning it back on restores them. You can also ask the Workbook Agent to turn live mode on with an interval, tell you how it is set, or turn it off.Publishing the setting doesn’t start any refreshes: a viewer opens the
dashboard with live mode off and enters it from the More actions menu
(
⋮).⋮)
lists Enter live mode right below Full screen. In a window narrower
than 920 pixels, which has no Full screen item, it sits right above
Duplicate instead. While live mode runs, the item reads Exit live mode,
and choosing it stops the refreshes. A dashboard published with live mode off
has the item only while an autoRefresh=<minutes> link runs
it, as Exit live mode; once that stops the refreshes, the item is gone.
While live mode runs:
- The interval counts from the end of the last refresh of the whole dashboard, including one started with Refresh all charts on the dashboard’s freshness leaf. Refreshing a single chart doesn’t restart it. A refresh still running when the next one comes due is never doubled: the interval starts again when it ends.
- Your control selections, cross-filters and open tabs are kept, and every refresh uses them.
- An Analysis widget is re-run only once it has run; one still running is left to finish. The re-run analysis stays in that browser tab and is not published, so other viewers keep seeing the published one.
- In a hidden browser tab, such as one behind another tab, nothing refreshes. Shown again after a refresh came due, the dashboard refreshes at once; shown sooner, it refreshes when the refresh is due.
- A refresh that succeeds shows no notice. One that fails shows the same notice Refresh all charts does, every time: Failed to refresh dashboard when a chart’s query failed, or Couldn’t load filter values when only a filter’s value list failed. The chart or filter that failed shows its error.
- It keeps running in full screen and after a reload, since it
is kept in the page’s address as an
autoRefreshparameter: Enter live mode addsautoRefresh=true, and a link’s own value stays as it was. A link copied with Copy link leaves it out.
Open a dashboard in live mode from a link
AddautoRefresh to a published dashboard’s address to open it in live mode:
autoRefresh=truerefreshes at the interval the dashboard was published with. On a dashboard published with live mode off, it refreshes nothing.autoRefresh=<minutes>, a whole number from 1 to 1440, refreshes every that many minutes, whatever the dashboard was published with.
⋮) while it runs,
and combines with fullscreen=true and the control
and tab parameters, so a link for a TV can read:
src.
Data freshness
Each widget shows a freshness leaf indicating how recently its data was refreshed. The dashboard’s own leaf reflects its least-recently-refreshed widget, so you can see at a glance whether everything on the dashboard is up to date.Linking between dashboards
Dashboards can link to one another. When a table widget shows a dimension that has links defined in the data model, left-clicking a cell opens a menu with those links: a drill-in link (dashboard:) navigates to
another dashboard in the same deployment, filtered by the values in the clicked
row, and an external link (url:) opens a URL. This is how you build
overview → detail flows — click a row in a summary dashboard to jump straight to
a focused dashboard scoped to that row.
Links are declared once on the dimension in the data model (not configured
per-dashboard), so every table that shows that dimension — in dashboards,
workbooks, embedded dashboards, and Explore — offers the same links. A drill-in
link targets a dashboard by its slug; see Dimensions →
Links to define them.
Cross-filtering
Turn on cross-filtering to let viewers of the published dashboard click a chart’s data to filter the other charts on it.Dashboard slug
A dashboard can have a slug — a short, stable, human-readable identifier (e.g.orders-detail) used to link to it from the data model. Data-model
dimension links with a dashboard: value reference a
dashboard by its slug to drill into it.
To set it, open the dashboard in the builder, open the options sidebar, and
fill the Slug field. Slugs are unique per deployment and are resolved
within the current deployment, so the same model works across environments. The
dashboard’s own URL is unaffected (it stays publicId-based).
There is no required order between the model and the dashboard. You can
reference a slug from a
dashboard: link in the data model before any dashboard
uses it, or set a dashboard’s slug before any link references it — neither
breaks. A link whose slug doesn’t (yet) resolve is simply skipped in the cell
menu, and starts working as soon as a dashboard in the deployment claims that
slug. (If you later clear or change a slug that links still reference, the
options sidebar warns you to update those links.)Download as PNG, PDF, or CSV
Open a published dashboard and click the Download button (the download icon) in the header. In a window narrower than 920 pixels, the header’s ⋮ menu holds a Download item instead. Either opens the Download settings dialog, which asks three things:- Format: PNG or PDF.
- Layout: Snapshot is the dashboard as on your screen: the open tab, the rows each table shows and the control widgets. Print version is the dashboard’s print version: every tab and every table row, with the control values listed at the top instead of the control widgets. Print version is PDF only: while PNG is picked, the option reads Print version (PDF only) and can’t be picked, and Snapshot is selected.
- Control values: Current, Default or Custom, the values the dashboard’s controls take in the file (see Control values in a download). This row appears only on a dashboard with at least one control, including one inside a container.
To export a single chart instead of the whole dashboard, hover the chart
widget, click its Download button (the download icon at the widget’s top
right), and choose Download as PNG or Download as PDF — the same menu
also offers Download as CSV for the chart’s underlying data. The image
captures just that chart, named after the chart’s title. On a table, the menu
also offers Download print version, directly under
Download as PDF. The widget’s ⋮ menu holds its other actions, not the
downloads.
PNG and PDF downloads are rendered on the server: Cube re-opens the dashboard
(or, for a single chart, that chart on its own), waits for rendering to finish,
and captures the result. This can take up to a couple of minutes for large
dashboards, and up to ten minutes for the print version of a
long table; the progress notice (
Preparing PDF…) stays up until the file
arrives. A single chart’s download carries your current control selections and
cross-filters; a whole-dashboard download carries the
values its Control values row picks. A scheduled notification has no browser
session, so its attachment renders the dashboard’s own defaults, unless that
notification carries selections of its own.
The CSV file is generated from the data already loaded in the chart. Download
as CSV opens a dialog where you choose the headers and the value format, with a
preview of the file. See Downloading results as
CSV.
To download the whole dashboard or export a single chart, you need the
Download data permission. Both are hidden entirely when an admin turns off
the account-wide data download controls. The same
screenshot mechanism powers PNG/PDF attachments on
notifications of a dashboard
delivery, and is also available programmatically — see
the Control Plane API.
Control values in a download
The Control values row of the Download settings dialog picks the values the dashboard’s controls take in the file:- Current (the default): the selections you have applied in your browser, for filters, time granularity switchers and field switchers alike, including the controls you added to the dashboard’s Dynamic controls widget, and your cross-filters.
- Default: every control takes the dashboard’s published default, as if you had just opened it. None of your selections, added controls or cross-filters is in the file.
- Custom: opens a Custom values card with one row per control, the same rows a schedule lists under Control values, each starting on Use default. A row on Use default takes the dashboard’s published default, Set to takes the value you pick, and Clear leaves the control unset. Your cross-filters are not part of a download with custom values, and the card says so when the page has any. While a row is on Set to with no value picked, Download is disabled with the reason “Pick a value for every control set to a value”. The ✕ on the card goes back to Current.
Print version
Print version, under Layout in the Download settings dialog, downloads the dashboard as a paper document rather than a picture of the screen. Where Snapshot captures the dashboard’s grid as it is laid out, the print version rebuilds it for A4 pages:- Page 1 opens with the dashboard’s title and, under it, one read-only line
stating the control selections the file was made with, each under the name
its control shows on the dashboard, for example:
Order date between 2016-01-01 – 2016-03-31 · Grouping = Users City · Parent = Default. A filter reads as its name followed directly by its condition, with no colon or=between them; a time granularity switcher, field switcher or parent control reads as its name,=and the value it holds. A control with no title is named as its header names it: an untitled filter by its field, which then opens its condition once (Status is completed), the others as Time granularity, Dimension or Measure, and Parent. Every control that holds a value contributes to that line, hidden ones included; a control holding none, such as a filter with an operator but no value, is left out. A filter whose default is resolved from the data is resolved for the print version too, so the line and the charts state the value it resolves to. Your cross-filters follow the controls on the same line, each as its field’s name and condition, for exampleStatus is completed. A dashboard with no control holding a value and no cross-filter prints no such line. - The controls themselves are left out, as is the Dynamic controls widget: no dropdown, picker or clear button appears on the page. A control a viewer added to that widget still states its value on the summary line under the title, as a placed one does.
- Every other widget — charts, tables, KPIs, text and Analysis widgets — prints full page width, one below another, in the order you read the dashboard: top to bottom, then left to right. Widgets inside a layout container print in the same flow, and a tabs container prints the widgets of every tab, in tab order, not only the tab on screen.
- A table prints every row its query returned, not only the rows its box shows on the dashboard, fitted to the page width and under the column names the dashboard shows. It continues onto the following pages with its column headers repeated at the top of each, and none of its rows is split between two pages.
- A chart, KPI, text or Analysis widget block that doesn’t fit in the space left on a page starts on the next page instead of being cut in two.
A table with a dimension in its pivot’s Columns or its measure names run
down the side (Pivots), or with totals,
subtotals or row grouping, prints as the grid the
dashboard shows: every row, the totals row included, under all its header
rows. Every row group prints expanded, including a group saved as collapsed.
layout: print on a PDF
dashboard export.