> For the complete documentation index, see [llms.txt](https://docs.visdom.virtuslab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visdom.virtuslab.com/visdom-control-plane/user-guide/dashboard-and-settings.md).

# Dashboard and settings

The suite's Home page and the settings every product shares.

## Dashboard

The Dashboard is the Home page of the whole suite. It does not store anything itself: every 30 seconds the browser asks each connected product for its summary, using the signed-in person's own token, and merges the answers. A person therefore sees only what they are allowed to see in each product.

It shows:

* **Status** – runs in progress, items that need attention, work done today, failures.
* **Usage and cost** – from AI Tracing.
* **Needs attention**, **In progress** and **Recently completed** lists across products.

The view follows the project selected in the switcher.

## Settings

The gear at the bottom of the module rail opens Settings from any product.

* **Appearance** – light, dark, or following the operating system, per person, applied in every product.
* **Workspace** – the timezone the whole suite uses for dates and schedules. Anyone can read it; admins change it. The UI offers common zones; the API accepts any IANA zone.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.visdom.virtuslab.com/visdom-control-plane/user-guide/dashboard-and-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.