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

# Dashboards

> What a dashboard is made of, and how one gets built.

A dashboard is a grid of widgets, each wired to a data source, refreshing on a shared schedule.

Dashboards are not assembled by hand. You ask for charts in [chat](/chat/overview), add the ones you
like, and ask for changes when something needs moving or restyling.

## Anatomy

| Piece          | What it is                                                                                           |
| -------------- | ---------------------------------------------------------------------------------------------------- |
| **Widgets**    | The charts, tables, KPIs and prose on the grid. See [Widgets](/dashboards/widgets).                  |
| **Parameters** | Dashboard-level filters and date ranges that widgets read. See [Parameters](/dashboards/parameters). |
| **Schedule**   | How often the data behind every widget is re-fetched. See [Refresh](/dashboards/refresh).            |
| **Context**    | A written summary of what the dashboard is for, kept for the agents that read it.                    |
| **Owner**      | One person. Scheduled refreshes run on the owner's connections.                                      |

## The grid

Widgets sit on a 12-column grid, and **the grid is not draggable**. There is no grab cursor and no
resize handle. Position and size are set by asking:

> Put the revenue chart top left, full width, and shorter.

That is the same division as everywhere else in Vistazo. You open the app to read and explore, and
Vistazo AI or your own agent is what builds and rearranges. It has a side benefit. Layout is written
down rather than nudged into place, so it survives a rebuild.

Empty cells compact upward, so you cannot leave a hole to create whitespace. Ask for a spacer instead
([Widgets](/dashboards/widgets#structure-headings-dividers-spacers)).

On a phone the grid becomes a single column. By default widgets stack in desktop reading order, top to
bottom then left to right, which can split things that belong together such as a column of KPIs beside
its chart. A widget can be given an explicit stack order to fix that.

<Warning>
  Stack order is all-or-nothing in one direction. Any widget carrying an explicit order sorts ahead of
  **every** widget without one, so setting it on one group hoists that group to the top of the phone
  layout. If you use it, order the whole dashboard.
</Warning>

## Context

Every dashboard carries a written summary of itself. It covers the dashboard's purpose, what it is used
for, caveats, and a plain-language reading of each widget. Vistazo keeps it current as the dashboard
changes.

This is what lets an agent answer "what does this dashboard say?" without reading every chart's raw
configuration. You can read it, and regenerate it, under **Settings → Context** on the dashboard.

<Note>
  Vistazo AI on the dashboard reads this summary too, which is why it can answer questions about a chart
  it did not build.
</Note>

## Ownership

A dashboard has exactly one owner, and ownership decides more than attribution. **Scheduled refreshes
run as the owner**, on the owner's data-source connections.

An editor can change the schedule and rewire a widget, but never lends the dashboard their own sources.
If the owner leaves the workspace, the schedule is disabled and says so rather than failing quietly.
Reassign it from **Settings → Sharing → Change owner**.

## Archiving

Archiving is reversible, and it lives as a danger-zone card at the bottom of **Settings → General**. An
archived dashboard stops refreshing and leaves the lists. Restoring it puts it back.

Archived widgets do not count against the per-dashboard widget cap. See [Limits](/reference/limits).