> 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.

Workflow Dashboard with run totals, success and fail rates, the runs chart and recent activity — The Workflow Dashboard — run totals, success/fail rates and recent activity for every workflow.

## 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 **New 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 toolbar also offers **Templates**, which opens the [Workflow Templates](/administration-and-setup/workflow/standard-workflow-builder.md#workflow-templates) library, and **Import Workflow**, which imports a workflow from a JSON file. 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:

## 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.docbits.com/administration-and-setup/workflow/workflow-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.