Introduction to dashboards in midPoint

Last modified 17 Sep 2025 22:03 +02:00
Dashboard feature
This page is an introduction to Dashboard midPoint feature. Please see the feature page for more details.
Table of Contents

Dashboards are a fundamental tool for efficient identity governance and administration (IGA) in your organization. They provide centralized overview of critical metrics, enabling managers to monitor compliance, track operational efficiency, and respond to risks proactively. You can configure dashboards based on the metrics that are important for you and your stakeholders.

Key motivations for using dashboards

  • Dashboards reduce operational overhead by automating data aggregation and presentation.

  • They help you spot potential risks more easily because they can highlight unwanted or non-compliant situations (e.g., users with accumulated high-risk access permissions)

  • You can configure as many different dashboards as you need for various roles who are interested in different metrics. For example, a security officer needs different data than the HR personnel.

  • You can customize the look and behavior of each dashboard: They can display custom data differently, use distinct color coding to show warnings, and so on.

Dashboards can show the number of active employees, failed resources, suspended tasks, and so on. You can make dashboards much more powerful than that, though. When you set them up to use collection domains and connect them with policy rules through object marks, you gain the ability to monitor compliance of your organization and receive warnings that an action is needed to put the situation back in line with requirements.

How dashboards help you stay compliant

Here is a simplified architectural outline showing how dashboards can help you with compliance through policy rules and notifications:

  • Policy Rules → Object marks → Object collections → Dashboards:

    • Policy rules define compliance criteria (e.g., users must not have both finance and HR roles).

    • Marks are added to objects that trigger (i.e., usually violate) the policy rule.

    • Collections aggregate objects marked by the policy rule.

    • Dashboards display the results, often with thresholds for visual alerts (e.g., red for critical violations).

  • Notifications:

    • Thresholds in collections can trigger notifications (e.g., email alerts) when compliance metrics exceed acceptable limits.

This architecture ensures compliance is a dynamic, actionable process integrated into your daily operations.

Reports created from dashboards

System administrators often like to get a daily report with operational statistics. If the data they are interested in are already shown in a dashboard, they do not need to duplicate the setup for their static report. They can use a dashboard report that takes the data from the configured dashboard and periodically generates a static report they can then conveniently receive, for example, via e-mail.

Further reading

See also

Compliance

This feature is related to the following compliance frameworks:

Was this page helpful?
YES NO
Thanks for your feedback