> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cube.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboards

> Curate and share polished views of your workbook reports with stakeholders as interactive dashboards.

Dashboards let you select and organize reports from your workbooks into polished, shareable views for your team and stakeholders. Transform your exploratory analysis into production-ready deliverables by choosing which insights to highlight and present.

## 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](https://docs.cube.dev/docs/explore-analyze/apps.md) with its own code
* **Present insights** – Showcase important discoveries in a polished, accessible format
* **Discuss results** – Ask questions and agree on answers in [comments](https://docs.cube.dev/docs/explore-analyze/dashboards/comments.md) on the dashboard or on one chart

## How it works

In the dashboard builder inside your [workbook][ref-workbooks], select the reports you want to include and arrange them on the canvas alongside other [widgets][ref-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](https://docs.cube.dev/docs/explore-analyze/dashboards/dashboards-as-code.md).

## 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](https://docs.cube.dev/docs/explore-analyze/dashboards/dashboards-as-code.md#4-publish)
performs over the API.

The button next to **Publish** reflects the dashboard's state — click it to open
the [revision history](#revision-history):

* **`v{N}`** — the published version and your draft match.
* **Draft** — you have unpublished changes.

Before the first publish, no button is shown.

A dashboard can require [review][ref-reviews] before it is published, even
before its first publish. Then **Publish** reads **Request review**, and the
dashboard can be published only after a reviewer approves the changes. While
the draft matches the review, a **Review** button that opens the review takes
the place of **Draft**, and shows before the first publish too.

While editing, **Undo** and **Redo** step through your draft changes, and
**Revert** discards all unpublished changes to restore the currently published
version.

### 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][ref-reviews]: 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](https://docs.cube.dev/embedding/iframe/dashboards.md).)

## Live updates

You don't have to reload to see a change made somewhere else: by an AI agent
connected through the [MCP server][ref-mcp-server], by another person, or by
you or the [Workbook Agent][ref-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][ref-cross-filtering], the [dynamic
  controls][ref-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.

If the connection drops, the page catches up when it reconnects or when you
return to its browser tab. [Embedded dashboards](https://docs.cube.dev/embedding/iframe/dashboards.md)
don't update live: they show a new publish the next time they load.

> [!WARNING]
>
> When a change arrives while an edit of yours in the dashboard builder is not
> saved yet, no dialog asks which one to keep:
>
> * On the dashboard draft, your edit is saved and replaces the change that
>   arrived.
> * On a chart, the change that arrived replaces your edit to that chart.

## 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](#full-screen-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](#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

Add `fullscreen=true` to a published dashboard's address to open it without the
sidebar, header and panels, for example on a TV:

```text theme={"dark"}
/d/<deployment_id>/dashboard/<dashboard_id>?fullscreen=true
```

The link doesn't switch the browser itself to full screen: on a desktop, use
the browser's own full-screen mode to hide its toolbar too. A reload keeps the
view, and **Esc** leaves it. In a window narrower than 920 pixels the link opens
the normal page, and widening the window to 920 pixels or more hides the
sidebar and header. Only the value `true` turns it on, and it combines
with the [control][ref-sharing-selection] and [tab][ref-tabs-url] 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](https://docs.cube.dev/embedding/iframe/dashboards.md#show-or-hide-header-controls) hides its
header with `showDashboardHeader=false` instead. Ask the [Dashboard
Agent][ref-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-link).

## 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](#data-freshness) leaf
does, and also re-runs every [Analysis widget][ref-analysis] that has already
run. It runs only in a browser tab that has the dashboard open. [Refreshes,
deliveries and alerts][ref-scheduled-refreshes] 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][ref-workbook-agent] to turn live
mode on with an interval, tell you how it is set, or turn it off.

> [!NOTE]
>
> 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
> (`⋮`).

On a dashboard published with live mode on, 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](#live-mode-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][ref-filter-values-failed] failed. The
  chart or filter that failed shows its error.
* It keeps running in [full screen](#full-screen) and after a reload, since it
  is kept in the page's address as an [`autoRefresh`](#live-mode-link)
  parameter: **Enter live mode** adds `autoRefresh=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

Add `autoRefresh` to a published dashboard's address to open it in live mode:

* `autoRefresh=true` refreshes 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.

Any other value is ignored, and the dashboard opens with live mode off. Either
form shows **Exit live mode** in the **More actions** menu (`⋮`) while it runs,
and combines with `fullscreen=true` and the [control][ref-sharing-selection]
and [tab][ref-tabs-url] parameters, so a link for a TV can read:

```text theme={"dark"}
/d/<deployment_id>/dashboard/<dashboard_id>?fullscreen=true&autoRefresh=10
```

Ask the [Dashboard Agent][ref-dashboard-agent] for a link to show the dashboard
on a TV and keep it refreshing, and it answers with such a link. An [embedded
dashboard](https://docs.cube.dev/embedding/iframe/dashboards.md#live-mode) takes the same parameter
in its iframe `src`.

## Data freshness

Each widget shows a [freshness](https://docs.cube.dev/docs/explore-analyze/workbooks/querying-data.md#result-freshness-and-provenance) 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.

[UI improvements for running queries and refreshing charts in Cube](https://www.youtube-nocookie.com/embed/9GZ_BqJ06DI)

[Results freshness indicator in cube](https://www.youtube-nocookie.com/embed/oycWBU4bpzo)

## Linking between dashboards

Dashboards can link to one another. When a table widget shows a dimension that
has [links][ref-dimension-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.

[Creating Dimension Links in Cube Dashboard Tables](https://www.youtube-nocookie.com/embed/r96fBtnK8c0)

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](#dashboard-slug); see [Dimensions →
Links][ref-dimension-links] to define them.

## Cross-filtering

Turn on [cross-filtering][ref-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][ref-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).

> [!NOTE]
>
> **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](#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](#control-values-in-a-download)). This row appears only on a
  dashboard with at least one control, including one inside a container.

Click **Download** to start. The dialog opens on **PDF**, **Snapshot** and
**Current** every time, whatever you picked at the last download. The file is
named after the dashboard's title. While a download of the dashboard is still
being prepared, **Download** is disabled with the reason "A download is already
in progress".

[Download dashboard charts as PNG or PDF in Cube](https://www.youtube-nocookie.com/embed/kQX7MwB194A)

[Export as CSV from Cube](https://www.youtube-nocookie.com/embed/ok75BJeJcAM)

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**](#print-a-single-table), 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](#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][ref-cross-filtering]; 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](https://docs.cube.dev/docs/explore-analyze/workbooks/querying-data.md#download-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][ref-data-download-controls]. The same
screenshot mechanism powers PNG/PDF attachments on
[notifications][ref-notifications] of a [dashboard
delivery][ref-scheduled-refreshes], and is also available programmatically — see
the [Control Plane API][ref-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][ref-controls]
  alike, including the controls you [added to the dashboard's Dynamic controls
  widget][ref-dynamic-controls], and your [cross-filters][ref-cross-filtering].
* **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][ref-schedule-controls],
  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**.

On a dashboard where no control can have a row (for example, its only controls
are a [parent control][ref-parent] and a filter whose visibility is
**Disabled**), **Custom** is disabled with the reason "No control on this
dashboard takes a custom value".

A **Snapshot** shows the open tab whichever values you pick. A **Print version**
states the picked values on the line under its title, so on **Default** the line
reads the published defaults.

### 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][ref-control-visibility] 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][ref-control-data-defaults] is resolved
  for the print version too, so the line and the charts state the value it
  resolves to. Your [cross-filters][ref-cross-filtering] follow the controls on
  the same line, each as its field's name and condition, for example
  `Status 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][ref-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][ref-layout] 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.

> [!NOTE]
>
> A table with a dimension in its pivot's **Columns** or its measure names run
> down the side (\[Pivots]\[ref-table-pivots]), or with \[totals]\[ref-table-totals],
> subtotals or \[row grouping]\[ref-table-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.

A print version larger than the export size limit isn't downloaded: the export
fails with a message asking you to narrow the dashboard's filters.

The print version takes the values the dialog's **Control values** row picks,
as a **Snapshot** does, and requires the same permission. A
[notification][ref-notifications] can attach it too: choose **PDF** under
**Attach dashboard as** and **Print version** under **Layout**. The [Control
Plane API][ref-control-plane-api] offers it as `layout: print` on a PDF
dashboard export.

#### Print a single table

To print one table rather than the whole dashboard, hover the table widget,
click its **Download** button, and choose **Download print version**, directly
under **Download as PDF**. The file is the same A4 document with that table
alone: page 1 opens with the dashboard's title and the line stating the control
selections, then the table prints every row as described above, and no other
widget of the dashboard is in the file. The table and the line follow your
current control selections, and a default [resolved from the
data][ref-control-data-defaults], as the whole-dashboard print version does. It
is named after the table's title.

The item appears on table widgets only, including a table inside a [layout
container][ref-layout]; other charts and KPIs keep **Download as PNG** and
**Download as PDF**. It is shown to the same viewers as the chart's **Download
as PDF**, under the **Download data** permission, and, like **Download as PNG**
and **Download as PDF**, it is unavailable while a chart's PNG, PDF or print
download on the dashboard is still being prepared. Notifications and the Control
Plane API print the whole dashboard only.

[ref-workbooks]: https://docs.cube.dev/docs/explore-analyze/workbooks

[ref-widgets]: https://docs.cube.dev/docs/explore-analyze/dashboards/widgets

[ref-reviews]: https://docs.cube.dev/docs/explore-analyze/dashboards/reviews.md

[ref-cross-filtering]: https://docs.cube.dev/docs/explore-analyze/dashboards/cross-filtering.md

[ref-controls]: https://docs.cube.dev/docs/explore-analyze/dashboards/widgets/controls.md

[ref-sharing-selection]: https://docs.cube.dev/docs/explore-analyze/dashboards/widgets/controls.md#sharing-the-current-selection

[ref-tabs-url]: https://docs.cube.dev/docs/explore-analyze/dashboards/widgets/layout.md#tabs-on-a-published-dashboard

[ref-dashboard-agent]: https://docs.cube.dev/docs/explore-analyze/dashboards/dashboard-agent.md

[ref-mcp-server]: https://docs.cube.dev/docs/integrations/mcp-server.md

[ref-workbook-agent]: https://docs.cube.dev/docs/explore-analyze/workbooks/workbook-agent.md

[ref-filter-values-failed]: https://docs.cube.dev/docs/explore-analyze/dashboards/widgets/controls.md#when-the-value-list-fails-to-load

[ref-dynamic-controls]: https://docs.cube.dev/docs/explore-analyze/dashboards/widgets/controls.md#dynamic-controls

[ref-control-visibility]: https://docs.cube.dev/docs/explore-analyze/dashboards/widgets/controls.md#visibility

[ref-control-data-defaults]: https://docs.cube.dev/docs/explore-analyze/dashboards/widgets/controls.md#defaults-resolved-from-the-data

[ref-layout]: https://docs.cube.dev/docs/explore-analyze/dashboards/widgets/layout.md

[ref-analysis]: https://docs.cube.dev/docs/explore-analyze/dashboards/widgets/analysis.md

[ref-table-pivots]: https://docs.cube.dev/docs/explore-analyze/charts/chart-types/table.md#pivots

[ref-table-totals]: https://docs.cube.dev/docs/explore-analyze/charts/chart-types/table.md#totals

[ref-table-row-grouping]: https://docs.cube.dev/docs/explore-analyze/charts/chart-types/table.md#row-grouping

[ref-dimension-links]: https://docs.cube.dev/docs/data-modeling/dimensions.md#links

[ref-notifications]: https://docs.cube.dev/docs/explore-analyze/dashboard-deliveries.md#notifications

[ref-scheduled-refreshes]: https://docs.cube.dev/docs/explore-analyze/dashboard-deliveries.md

[ref-data-download-controls]: https://docs.cube.dev/admin/users-and-permissions/roles-and-permissions.md#restricting-data-downloads

[ref-control-plane-api]: https://docs.cube.dev/reference/control-plane-api.md#apiv1deploymentsdeployment_iddashboard-exports

[ref-parent]: https://docs.cube.dev/docs/explore-analyze/dashboards/widgets/controls.md#parent

[ref-schedule-controls]: https://docs.cube.dev/docs/explore-analyze/dashboard-deliveries.md#control-values


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.