> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-automate/backoffice/dashboard.md).
# Use the Dashboard
Check automation status, recent runs, and pending approvals from the dashboard.
The dashboard is the landing page of the **Automation** section. Use it to get an at-a-glance view of automation activity across all workspaces you can access.
The Automation dashboard.
## Status Cards
The dashboard shows a row of cards that count automations and runs across the workspaces you can access:
| Card | Shows |
| --------------- | ----------------------------------------------------------------------- |
| **Published** | Automations that are currently published. |
| **Draft** | Automations that have unpublished changes or have never been published. |
| **Inactive** | Automations that have been explicitly disabled. |
| **Failed Runs** | Recent runs that ended in the Failed state. |
| **In Progress** | Recent runs that are still Running or Suspended. |
## Recent Activity
Below the cards, the **Recent Activity** list shows the most recent runs across all your workspaces. Each entry shows the automation name, the run status, and when the run started. Click an entry to open the run detail view.
## First-Run Welcome
When no automations exist yet, the dashboard shows a welcome panel. The panel links straight to creating a workspace.
## See Also
* [Review Runs](/umbraco-automate/backoffice/runs.md)
* [Use Approvals](/umbraco-automate/backoffice/approvals.md)
* [Create Your First Automation](/umbraco-automate/getting-started/first-automation.md)
---
# 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.umbraco.com/umbraco-automate/backoffice/dashboard.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.
