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

# Dashboards

> Save the columns, filters, and sort you use on Conversations as named dashboards and switch between them.

A **dashboard** is a saved layout of the Conversations table: which columns it shows, in what
order, plus the filters, the sort, and the page size that go with them. Selecting a dashboard
swaps all of that at once.

Make one for each way your team reads the history - *Failed calls*, *WhatsApp only*, *Lead
quality* - instead of re-applying the same filters every morning.

## The Dashboard button

One button in the page header, bottom-right of the header card, names the dashboard you are on.
It is the whole control:

| Open it and you get   | What is there                                                                                                      |
| --------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **The column editor** | The columns this dashboard shows - reorder, add, remove - with the name editable in place, over **Discard · Save** |
| **All dashboards**    | Every dashboard in the workspace, each with a **⋯** menu, and **＋ Create dashboard** at the bottom                 |

The **⋯** menu acts on its own row, not on the dashboard you are currently viewing - so you can
set another dashboard as your default, or delete one, without switching to it first.

## Choose the columns

The editor lists everything the table can show, grouped:

| Group               | Columns                                                         |
| ------------------- | --------------------------------------------------------------- |
| **Call**            | Direction, Agent, Channel, Origin, From, To, Started, Recording |
| **Identity**        | Call ID, Provider Call ID, Agent ID, Agent Version, Batch ID    |
| **Outcome**         | Status, Ended Reason                                            |
| **Cost**            | Usage, Cost                                                     |
| **Timing**          | Connected, Connect Time, Ended                                  |
| **Custom Analysis** | One column per item in your workspace's Custom Analysis library |

Ticking a column changes the table behind the editor, so you can see the result while you choose.
Columns that hold text - Agent, and every Custom Analysis value - size themselves to the rows
currently on screen, so their width changes as you page or filter. That is intentional: one width
cannot serve both a one-word answer and a three-sentence summary.

<Note>
  If you remove every column, the rows are still listed and still open when clicked - you are not
  locked out of a dashboard whose columns you emptied by accident.
</Note>

### Custom Analysis columns

An item from your [Custom Analysis](/building-agents/custom-analysis) library becomes available as
a column once its group is attached to an agent, or once it has produced a value on a conversation.
Definitions that have never been used stay out of the list.

A cell shows the extracted value, or the status word when the group was **skipped** or **failed** -
a gated group is a different fact from an empty answer. WhatsApp threads show a dash; they carry no
analysis.

These columns cannot be sorted or filtered on. Renaming an item in the library re-labels the
column rather than breaking it, and disabling an item keeps its historical column intact.

## Nothing saves by itself

Changing columns, filters, or sort marks the dashboard **Unsaved** and offers **Save** and
**Discard**. Until you press Save, the change is yours alone and a page reload returns to the
saved version.

This is deliberate: every dashboard belongs to the whole workspace, so an autosave would change
what a colleague is reading mid-scroll.

* On a dashboard someone made, **Save** updates it for everyone.
* On the built-in dashboard the button reads **Save as new** - the built-in is forked, never
  overwritten.
* If someone else changed the dashboard while you had it open, Save tells you so instead of
  quietly overwriting their work.
* Switching dashboards while you have unsaved changes drops them. The dashboard you picked is the
  one you get.

## Who can do what

Every dashboard belongs to the workspace. There are no private dashboards.

| Action                             | Who                                                        |
| ---------------------------------- | ---------------------------------------------------------- |
| See every dashboard                | Anyone who can read Conversations                          |
| Create one                         | Anyone who can read Conversations                          |
| Edit one, including someone else's | Anyone who can read Conversations                          |
| **Duplicate** one                  | Anyone - the way to fork a colleague's without changing it |
| **Delete** one                     | Its author, or a workspace admin                           |

Where an action is not available, the menu says why rather than leaving a gap.

## Your default and your order

Two things are **personal to you**, not shared: which dashboard opens by default, and the order
they appear in the list. Setting a default with **⋯ → Set as default** changes nothing for anyone
else.

Deleting the dashboard that was your default moves the star back to the built-in one.

## The built-in dashboard

Exactly one ships with Vocily - **Conversations**, tagged **Default**. It shows:

> Agent · Agent Version · Direction · From · To · Status · Usage · Cost · Started

It exists so there is something on screen before anyone has saved anything, and so **Discard** has
somewhere to land. It cannot be renamed or deleted, but you can duplicate it and you can set it as
your personal default.

## Share a dashboard

The dashboard is in the page URL as `?view=…`, so a link opens on the same one. Links that carry
their own filters - from a billing transaction, for example - apply on top of the dashboard you
are on and show as unsaved, so you can keep them with **Save as new**.

## Limits

| Limit                            | Value         |
| -------------------------------- | ------------- |
| Dashboards per person, per table | 50            |
| Columns in one dashboard         | 40            |
| Dashboard name                   | 80 characters |

## On narrow screens

Below roughly 1300px the page switches to stacked cards, which have no columns. The active
dashboard still supplies the **filters and sort**; the column set simply does not apply.

## What's next

* [Conversation history](/conversations/history) - the table itself, its filters and statuses.
* [Custom Analysis](/building-agents/custom-analysis) - define the items that become columns.