Understanding the Policy Details Page
The policy details page shows everything the dashboard knows about a single policy: how often it fired, what it did, who triggered it, and where.
The Policy Effectiveness tab tells you which policies are busy. This page tells you why. It is where you go once a chart has shown you a policy worth investigating.
You can reach it three ways, and all three land on the same page:
- Click a bar in the DLP Policies chart
- Click a bar in the Access Control Policies chart
- Click Open on a row in the By Classification list
Finding your way back
The breadcrumb at the top shows Policy Effectiveness followed by the policy name. Click Policy Effectiveness to return to the tab.
Below the policy name, a line gives the policy type and the reporting period, for example DLP and Last 7 Days. The period is inherited from the tab you came from.
What the page contains
| Area | What it shows |
|---|---|
| Severity badge | Beside the policy name on a data security policy, for example High. Access policies do not carry one |
| Summary cards | Four figures. Two are the same whatever the policy type, and two depend on it |
| Top Users | A bar chart ranking the people who triggered the policy most |
| By AI Tool | A bar chart showing where the policy was triggered |
Reading the summary cards
The first and third cards are the same for every policy:
| Card | What it tells you |
|---|---|
| Hits | How many times the policy was triggered in the period, with an arrow comparing it against the previous period of the same length |
| Active Users | How many people triggered it |
The second and fourth cards depend on the type of policy you opened:
| Position | On a data security policy | On an access policy |
|---|---|---|
| Second card | Action - what was done with the content, for example Quarantine with note | Verdict - whether the calls were allowed or denied |
| Fourth card | Tools - how many tools were involved | AI Tools - how many were involved |
Reading Top Users
This chart names the people who triggered the policy most often, ranked highest first.
It is the fastest route from a policy that looks alarming to the conversation you actually need to have. A policy with a high hit count concentrated on one or two people is usually a workflow problem rather than an organisation-wide one.
Reading By AI Tool
This chart shows where the policy was triggered, ranked by hit count.
On a data security policy, the bars are the AI applications the content passed through.
On an access policy, the bars are the individual tool calls the policy matched, such as a call that adds a comment to a Jira issue.
What you can do from here
- See how often a single policy fired, and whether that is rising or falling
- Confirm what the policy actually does when it matches
- Identify the people triggering it most
- See which applications or tool calls are involved
- Return to the Policy Effectiveness tab using the breadcrumb