> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/product-specifications/support-functions/13.-performance-management.md).

# 15. Performance management

OpenCRVS dashboards leverage the power of Metabase to transform civil registration data into insightful visualisations.\
\
Any data field configured with `analytics=true` will be available in Metabase. Each dashboard is highly customisable, allowing users to create and integrate various data views to suit their specific needs.

Helping performance managers understand how their system and workflows are performing and inform targeted corrective action. To ensure they are on target to achieving universal registration rates.

### **Configuration options**

* Create n number of Metabase dashboards. Each dasboard shows as a menu option in the OpenCRVS side nav.
* Add/remove performance dashboards visualisations using Metabase interfaces
* Control who can see Metabase Performance Dashboards with `scope:performance.read`


---

# 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, and the optional `goal` query parameter:

```
GET https://documentation.opencrvs.org/product-specifications/support-functions/13.-performance-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
