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

# The Charts View

> Rearrange the default Charts view — reorder and hide sections, move charts between them, and create custom sections, saved for everyone on the project.

The **Charts** view is the default view of a project. It automatically includes every metric your runs log, grouped into sections by metric prefix — so a newly logged metric shows up without anyone configuring anything.

You can rearrange that view: reorder and hide sections, move charts between sections, and add your own sections. The arrangement is saved on the project and shared with everyone in your organization.

## Charts view vs. dashboards

Both show charts, but they answer different questions.

|              | **Charts view**                                                | **[Dashboards](/pluto/dashboards)**                                                                         |
| ------------ | -------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| What's on it | Everything you log — metrics, histograms, media, tables, files | Most of those, but not custom charts, tables, or interactive files                                          |
| New data     | Automatic, always                                              | Automatic inside [dynamic sections and widgets](/pluto/dashboards#dynamic-content); otherwise added by hand |
| Layout       | Rearrange a fixed set — reorder, regroup, hide whole sections  | Choose which widgets exist and what goes in each one                                                        |
| Scope        | One per project                                                | As many as you want                                                                                         |

The key difference is **coverage without configuration**. A dashboard can keep up with new data too — that's what [dynamic sections and widgets](/pluto/dashboards#dynamic-content) are for — but it does so within the patterns you chose, so anything logged outside those patterns won't appear. The Charts view has no patterns to fall outside of.

### What appears in the Charts view

Effectively everything you log:

* **Scalar metrics** — a line chart per metric
* **[String metrics](/pluto/visualizations/lines#string-metrics)** — drawn as a staircase
* **[Histograms](/pluto/visualizations/histograms)**
* **[Images](/pluto/visualizations/images)**, **[video](/pluto/visualizations/video)** and **[audio](/pluto/visualizations/audio)** — images can also carry bounding-box and mask [annotations](/pluto/visualizations/images#annotations)
* **Tables**, and logged files — Plotly and matplotlib figures, 3D point clouds, HTML and plain text

### How sections are named

A section is the log name's **prefix** — everything before the last `/`. So `train/loss` and `train/acc` share a `train` section, and `eval/per_class/cat` lands in `eval/per_class`.

A name with no slash has no prefix to group by, so it falls back to a section named after the kind of data it holds — `metrics`, `media`, `histogram`, `table` or `files`. That's why a bare `output.log` shows up under `files` rather than beside your metrics.

<Note>
  On the all-runs Charts view, files and text are grouped with **media** rather than in their own `files` section; the individual run page keeps them separate.
</Note>

Two things you can put on a dashboard have no Charts view equivalent at all:

* **[Logs](/pluto/logs)** — console output isn't a per-step log, so it has no Charts view section. Read it on the run's **Logs** tab, or add a logs widget from the **Files** tab of **Add Widget**.
* **[Bar charts](/pluto/visualizations/bar-charts)** — added from the **Distributions** tab. The sibling scalars behind one *do* appear in the Charts view as individual line charts; the rollup itself is something you add explicitly.

Reach for a dashboard when you want a curated view built around specific questions. Reach for the Charts view when you want the guarantee that nothing is missing.

## Editing the layout

Click **Edit layout** above the charts. The view stays in place and becomes directly editable — the charts you're rearranging are the real charts, at their real size.

While editing, a control bar stays pinned at the top of the view as you scroll:

* **Add section** — create a custom section.
* **Reset** — clear the saved arrangement and return to the default.
* **Cancel** — discard your changes.
* **Save layout** — save for everyone on the project. Disabled until you change something.

### Reordering and hiding sections

Drag a **section header** to move that section up or down.

Each section header also has an **eye toggle**. Click it to hide a section from the view; click again to show it. Hiding is part of the saved layout, so it applies for everyone.

<Tip>
  Hiding a section doesn't stop the metrics being logged or affect the data in any way — it only removes the section from this view. You can always unhide it from **Edit layout**.
</Tip>

Hiding works on **whole sections only**. There's no way to hide a single chart — the Charts view's guarantee is that every metric is present, so individual charts can be moved and reordered but never removed. If you want a view with only certain charts on it, build a [dashboard](/pluto/dashboards) instead.

### Moving charts between sections

Two ways, both in edit mode:

* **Drag** a chart onto another chart, or onto the body of another section.
* Use the **Move to section…** menu on the chart card. It's searchable, which is faster when the target section is far down a long view.

The move menu also offers **New section…**, which creates a section and moves the chart into it in one step.

### Custom sections

**Add section** creates an empty section — name it, then move charts into it.

Custom sections can be **renamed** and **deleted** from their header. Sections derived automatically from metric prefixes keep their computed name and can't be renamed.

Deleting a custom section never deletes charts: each chart returns to the section it would have been in automatically. Metrics logged later still land in their derived section, not in your custom one.

## Where the layout applies

The saved layout is stored **per project and shared across your organization** — the same way custom dashboards are. Everyone opening the project sees the arrangement you saved, and it persists between sessions.

The individual run page inherits the same arrangement, read-only. Edit the layout from the project's Charts view and the run page follows.

Two things stay per-user and are **not** part of the saved layout:

* **Collapsing a section** with its chevron. Sections always start expanded, so you can confirm at a glance that everything is being ingested.
* Anything you change from a chart's own settings popover, such as [histogram axis bounds](/pluto/visualizations/histograms#settings).