Actor Bypass Fingerprint(3.1.10)

Governance failures always have an author. This visual identifies which specific accounts are responsible for the most bypass events — the transitions that skipped required workflow steps or violated permitted paths. It combines bypass count and reopen contribution into a single risk score per actor.

Where events cannot be attributed to a known actor, they cannot be reconstructed after the fact. A DORA or NIS2 reviewer asking "who made this change?" would have no answer for these events. This visual provides the forensic trail that auditors need.

What you can conclude

• An actor at the top of this list with a high bypass count should be part of a direct compliance conversation — are they aware of the workflow rules, or are they bypassing them knowingly?
• A service account or integration appearing high on this list is a security concern — automated processes should not be bypassing workflow governance.
• A broad distribution of bypass events across many actors suggests a process design problem rather than individual non-compliance.

How this chart works

Horizontal bar chart ranking actors by risk contribution score (bypass events × weight + reopen contribution × weight), with a supporting donut chart showing bypass event share. Account IDs are shown by default; display names require additional configuration.