> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/workflows/monitoring-workflows-dashboard.md).
# Monitoring Workflows dashboard
The Workflows overview page gives IT teams visibility into workflow execution and outcomes. View summary results, examine execution details, and troubleshoot issues directly from the dashboard, with real-time records captured for every triggered workflow.
## Accessing the Workflow overview page
To access the workflow **Executions** details:
1. Go to **Workflows** > **Manage workflows**.
2. Click on the target workflow to open the **Edit Workflow** page.
3. From the workflow designer, click the **Workflow overview** button in the top-right corner of the page to view workflow **Executions**.
You can also access the dashboard directly from the **Workflow configuration** page if the workflow has been enabled.
{% hint style="info" %}
Alternatively, simply select a listed workflow from the **Workflow** navigation menu to access
**Workflow Overview** dashboard.
{% endhint %}
---
# 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.nexthink.com/user-guide/workflows/monitoring-workflows-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.
