> For the complete documentation index, see [llms.txt](https://docs.controlbee.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.controlbee.nl/controlbee-docs/en/readme.md).
# Dashboard
The dashboard provides an overview of the current statuses of the controls, processes, risks and actions.
## Dashboard explanation
* The **control status** shows the extent to which the controls have been implemented. The control status can optionally be filtered based on a source linked to the controls. In addition, it can be filtered on labels linked to the controls.
* The **KPI status** shows the latest known scores of the KPIs in the management system. These KPIs can be filtered per objective.
* The **process status** is about how long the process is still valid and when the process must be audited again.
* The **risk status** shows when the risks must be evaluated. The risk status can be filtered based on policy, risk owners and linked labels.
* The **action status** shows how many actions are open and how far the target date still lies in the future. In addition, the action status can be filtered on assignees, the linked labels and on action types.
* The **risk matrix** shows where all valid risks are located based on likelihood × impact. This gives the organization insight into which risks it is still exposed to. The risks in the risk matrix can also be filtered on policy, risk owners and linked labels.
{% hint style="info" %}
The dashboard and the risk matrix include a drill-down function.
{% endhint %}
{% hint style="warning" %}
Please note: if there are multiple contexts present in the company concerned, the dashboard shows the status of all open actions across all contexts.
{% 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.controlbee.nl/controlbee-docs/en/readme.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.
