> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/investigate/dashboards-and-alerts.md).
# Dashboards
Learn how to build custom dashboards using groundcover
Dashboards let you build **persistent, shareable views** over your observability data. Use them for on-call playbooks, service health boards, incident investigation layouts, and any view you want to revisit without rebuilding queries in Explore.
Dashboards are built from **widgets** (charts, tables, stats, text, and grouped sections), filtered with **variables**, and scoped to a **time range**. Changes are saved per dashboard and can be shared with your team.
Easily create a new Dashboard [using our guide](/investigate/dashboards-and-alerts/create-a-dashboard.md).
You can also install a ready-made dashboard from the [Dashboard Catalog](/investigate/dashboards-and-alerts/dashboard-catalog.md), a library of pre-built dashboards that groundcover manages and keeps current automatically.
## Find your frequently used dashboards
Mark dashboards as favorites to filter the Dashboards list to your selection, or pin them to the sidebar for direct access. For example, pin the service health dashboard you check throughout an on-call shift, and favorite the other dashboards for services you own.
Favorites and pins are personal: they don't affect other users or change the dashboard's content. You can use either or both on a dashboard, including managed dashboards, even with read-only access. Pinning a dashboard does not automatically add it to your favorites.
### Add a dashboard to favorites
1. Open a dashboard and click the star beside its name. You can also select **Add to favorites** from its **Actions** menu or from the dashboard's menu in the Dashboards list.
2. Return to the **Dashboards** page and enable **Favorites only** to show your favorite dashboards.
Turn off **Favorites only** to return to the full list with your other filters still applied.
### Remove a dashboard from favorites
Open the dashboard and click the filled star beside its name, or select **Actions → Remove from favorites**. You can also select **Remove from favorites** from the dashboard's menu in the Dashboards list.
Removing a favorite does not delete the dashboard or remove its sidebar pin.
### Pin a dashboard to the sidebar
1. Open a dashboard and select **Actions → Pin to sidebar**. You can also select **Pin to sidebar** from the dashboard's menu in the Dashboards list.
2. The dashboard appears under **Pinned** in the left sidebar. Click its name to open it directly.
Pinned dashboards in the left sidebar.
### Unpin a dashboard from the sidebar
1. Hover over the dashboard under **Pinned** in the left sidebar and open its menu.
2. Select **Remove from sidebar**.
You can also open the dashboard and select **Actions → Remove from sidebar**, or select **Remove from sidebar** from its menu in the Dashboards list. Removing a pin does not delete the dashboard or remove it from your favorites.
### Reorder pinned dashboards
1. Hover over a dashboard under **Pinned** in the left sidebar to reveal its drag handle.
2. Drag the handle to move the dashboard above or below another pinned dashboard.
The new order applies only to your sidebar.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.groundcover.com/investigate/dashboards-and-alerts.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
