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

# Dashboards

> The dashboard format: a composed homepage for your brain — live counts, lists, tables, and charts over your documents.

A dashboard is a homepage for your brain: live numbers, lists, and charts over your documents, mixed with curated links and a note or two. It is the page you point a new teammate at, and the page you open on a Monday to see whether your knowledge is in good shape.

Like a [base](/formats/base), a dashboard stores questions rather than answers. Every block re-runs live: write a document tomorrow and the counts, lists, and charts already include it.

## Creating a dashboard

Ask your agent, and describe the page you want:

> "Build me a home dashboard: document counts up top, what needs review, our key playbooks as cards, and quick links to the ICP and pricing."

Like bases, dashboards have no menu item because describing one is faster than assembling one. Your agent lays it out and maintains it — ask for another block, a different chart, a tighter filter, and it rearranges the page.

## The blocks

A dashboard is rows of one to three blocks. Nine kinds exist:

| Block | Shows |
| - | - |
| **Stat** | One number — a count of matching documents, or a total or average of a property. "Documents: 214". "Pipeline (\$M): 4.2". |
| **Ratio** | A share, with a meter. "Docs with an owner: 87%". |
| **List** | Compact document rows with one detail column. "Recently updated". "Needs review". |
| **Table** | An embedded read-only grid with the columns you choose. |
| **Cards** | Documents as cards, with description and tags. "Our playbooks". |
| **Bar** | Top groups by count for any property. "Docs by type". |
| **Links** | Curated navigation. "Start here: ICP · Pricing · Support playbook". |
| **Prose** | Free text with links — a welcome note, house rules. |
| **Callout** | Emphasised text. "Pricing changes Friday". |

Blocks that ask a question select documents exactly the way a base does — by type, folder, tags, owner, freshness, or any extra property — and can carry a "See all" link through to a fuller document.

## Working with a dashboard

A dashboard is for reading: click a stat's "See all", open any document listed, follow a link. To change it — add a block, adjust a query, reorder the rows — ask your agent.

Because a dashboard is an ordinary document, your agents can also **read** it as context. That is worth more than it sounds: it is a standing, grounded statement of what your team treats as its vital signs and its starting points, and any agent working in your brain can see it.

## Good dashboards to ask for

* **A team home.** Document and folder counts, recently updated, curated "start here" links, and a welcome note for new teammates.
* **A maintenance console.** Stale documents, unowned documents, untagged documents — the health of your brain at a glance. This is the one that keeps a brain honest.
* **A domain overview.** Scoped to a single folder — a sales home with pipeline stats, the competitor view, and the playbook cards.

<Note>
  Dashboards pair well with [bases](/formats/base): keep the deep, tabbed working view as a base, and point a dashboard block's "See all" link at it.
</Note>

<Columns cols={2}>
  <Card title="Bases" icon="layers" href="/formats/base">
    The deeper, tabbed working view behind a dashboard block.
  </Card>

  <Card title="Document formats" icon="table" href="/formats/overview">
    All six formats, and which to pick.
  </Card>
</Columns>


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