> ## Documentation Index > Fetch the complete documentation index at: https://docs.zespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Finding your way around the dashboard > The sidebar has 21 fixed rows in five groups. Related pages share one row with tabs, Policies, Compliance and Audit log are the Govern group, project Settings sits under the gear at the bottom, and a Set up chip marks features you have not started yet. The sidebar in a project has **21 rows**, always in the same place. A row never moves, hides or changes group on its own. Only you change the sidebar: collapse a group, or pin up to five rows to the top (hover a row and select the bookmark, or focus it and press `P`). ## Keyboard shortcuts on rows Rows with a shortcut show it in a tooltip, not on the row. Rest the pointer on a row, or move keyboard focus to it, and after about half a second a small tooltip opens to the right of the sidebar with the page name and one key chip, for example **Traces** and **G T** (press `g`, release, then press `t`). Only one tooltip is open at a time; once you have seen one, the next row's tooltip opens at once. It closes when you move away, scroll, press `Esc` or click. On hover the row itself shows only its count badge (if it has one) and the pin button, side by side without overlap. In the narrow icon-only sidebar the same tooltip carries the page name and chip, so each row has one tooltip. ZespanPilot shows its own shortcut, `Cmd+J`. ## The five groups | Group | Rows | | - | - | | **ZespanPilot** (no heading) | ZespanPilot | | **Observe** | Overview, Traces, Sessions, Agents, Tools, Models, Users, Performance, Costs | | **Fix** | Issues, Incidents, Alerts, Changes | | **Improve** | Evaluations, Guardrails, Test lab, Prompts | | **Govern** | [Policies](https://docs.zespan.com/dashboard/policies.md), [Compliance](https://docs.zespan.com/compliance/evidence-packs.md), Audit log | All groups start open, including **Govern** the first time you see it. If you collapsed the group that holds the page you are on, it opens again to show that page. **Policies** and **Compliance** show their plan name when your plan does not include them; selecting one still opens the page, which explains what the plan adds. **Prevention** is not a page of its own: prevention drafts and proposals appear on **Policies** and in the cause card on each [issue](https://docs.zespan.com/dashboard/issues.md). ## Rows with tabs Pages that belong together share one row and a tab strip under the page title. Every page keeps its own address, so existing bookmarks and links still work, and the row is highlighted on each of its tabs. The command palette (`Cmd+K`) still lists every page by its own name. | Row | Tabs | | - | - | | **Costs** | Explorer, Attribution, Value, Forecasts | | **Issues** | Issues, [Errors](https://docs.zespan.com/dashboard/errors.md) | | **Test lab** | [Simulations](https://docs.zespan.com/dashboard/simulations.md), [Datasets](https://docs.zespan.com/dashboard/datasets.md), [Annotations](https://docs.zespan.com/dashboard/annotation-queues.md) | | **Prompts** | Prompts, [Playground](https://docs.zespan.com/dashboard/playground.md) | A tab your plan does not include shows the plan name next to its label. Selecting it still opens the page, which explains what the plan adds. A row opens its first tab your plan includes: on the Pro plan, **Test lab** opens Datasets, because Simulations needs the Team plan. > [!NOTE] > > **Test lab** is a row, not a page. There is no `/test-lab` page to open or bookmark; use Simulations, Datasets or Annotations. ## Pins on your first visit Until you pin, unpin or collapse something, the sidebar shows no pins and every group open. If you answered **What do you mostly do?** at the end of onboarding, the first visit starts with up to three rows pinned for that answer (for example Issues, Incidents and Alerts for On-call). Saved sidebar preferences always win: a returning user sees no change, and changing your answer later in [Profile](https://docs.zespan.com/account/profile.md) never moves your rows. Your answer never hides a page. ## Settings and Instrumentation These two pages are under the **gear** next to your account at the bottom of the sidebar. Select it to open a menu with **Settings** and **Instrumentation**. The gear is highlighted while you are on either of them or anywhere under Settings. They are also in the command palette. **Compliance** and **Audit log** used to be in this menu; they are now rows in the **Govern** group, and **Policies** is a row of its own instead of a tab of Guardrails. Every page keeps its address, so links and bookmarks still work. A pin you saved on Policies, Compliance or Audit log stays pinned, and sidebar preferences saved in your browser are migrated the first time you open the dashboard (your collapsed groups stay collapsed). ## The "Set up" chip A row shows a small **Set up** chip, and its label turns a quieter grey, when that feature has never been used in the project: | Row | Shows "Set up" until | | - | - | | Sessions | a trace has carried a session id | | Users | a trace has carried a user id | | Tools | a tool call has been recorded | | Costs | a model call with a price has been recorded | | Evaluations | an evaluator exists, or evaluation scores have been sent from the SDK | | Guardrails | a guardrail or a policy exists, or a guardrail check has been recorded | | Alerts | you have created or enabled an alert rule (an alert rule Zespan drafted for you does not count until you enable it) | | Test lab | a dataset, a simulation scenario or an annotation queue exists | | Prompts | a prompt exists | The chip is a hint, not a lock: the row stays where it is and the page opens normally, with an explanation of what feeds it. Once a feature has been used it never goes back to "Set up", even if you later delete its data. If Zespan cannot tell whether a feature has been set up, for example while the page loads or when a check fails, the chip is left off. The demo project never shows it. > [!NOTE] > > Checks look at everything the project has recorded that your plan still keeps, and disabled items count. A chip for something you create in the dashboard (an evaluator, a guardrail, an alert rule, a dataset, a prompt) clears the next time you open a page. A chip for trace data (Sessions, Users, Tools, Costs) can take a few minutes to clear after your first event arrives. ## Next steps > [card] [Overview](https://docs.zespan.com/dashboard/overview.md) > > The health page you land on, and the product tour. > [card] [Glossary](https://docs.zespan.com/reference/glossary.md) > > What each word in the sidebar means. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.