> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/workflow/workflow-dashboard.md).

# Dashboard

The **Workflow Dashboard** is the home of the workflow area. It shows how your workflows are performing — run totals, success and fail rates, a runs-over-time chart and recent activity — and gives you access to the workflow list, the test manager and the Card SDK.

<figure><img src="/files/XqcAd2Bah0sYsSoLSepP" alt="Workflow Dashboard with run totals, success and fail rates, the runs chart and recent activity"><figcaption><p>The Workflow Dashboard — run totals, success/fail rates and recent activity for every workflow.</p></figcaption></figure>

## Tabs

* **Dashboard** — run metrics and recent activity (shown above).
* **Workflow List** — every workflow with its type, execution order and trigger. Create a new one with **Add Workflow**.
* **Test Manager List** — test scenarios that validate your workflows; run them with **Run All Tests**.
* **License** — workflow licensing information.
* **Card SDK** — build and upload custom workflow cards (see [Card SDK](/administration-and-setup/workflow/card-sdk.md)).

The **Test Manager** lets you save test scenarios per workflow and run them together, so you can confirm your workflows still behave correctly after changes:

<figure><img src="/files/Byww3U34F6eRDUcZhWJ9" alt="Workflow Test Manager List with test scenarios and Run All Tests"><figcaption><p>The Test Manager List — each scenario shows a pass/fail result; use <strong>Run All Tests</strong> to re-run them all.</p></figcaption></figure>

## Next steps

* Build a linear automation with the **Standard Workflow** builder.
* Build a branching flow with the **Advanced Workflow** builder.


---

# 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:

```
GET https://docs.docbits.com/administration-and-setup/workflow/workflow-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.