How controls are evaluated
Updated on 10 November 2026.
This page explains how the Browser Extension picks the one control that applies to a user's action in the browser, and what changes the result. You manage controls under Govern > Policy Engine > Endpoint Agent > Browser; see Browser controls.
Key terms
How the extension decides, step by step
- Download the controls. At startup and every 2 minutes, the extension downloads every enabled System and Custom control.
- Detect the action. It checks only controls whose use case covers that kind of action, so a paste control is not checked when the user submits a prompt. A post into a website chatbot can also match Users Leaking Sensitive Data controls. See Which control wins when several match.
- Check the conditions. A control matches when all of its conditions are true. QuilrAI checks content for sensitive data using your Detection Models.
- Remove excused controls. It drops controls excused for this app or person, for example by a turned-off detection or an approved action request, and controls whose popup has reached its prompt frequency limit.
- Pick one winner. It ranks the rest by risk behavior, then by criticality, and applies only the first.
- Apply the winner.
- Monitor: the action goes ahead and a finding is recorded.
- Enforce: the Just in Time action applies, unless the user already gave a reason or acknowledged a notice for the same risk behavior in that tab and site. See What changes the outcome for an app or a person.
- Enforce without a Just in Time action: the user is not interrupted. Chromium-based browsers and Firefox record a finding, and Safari records nothing.
The finding in Findings & Interactions names the winning control.
How conditions are checked
Inside a group, rows combine from top to bottom, and AND does not take precedence over OR. See How conditions combine.
Every browser ignores a control whose top-level condition cards are joined with OR, although the console saves it and shows it as enabled. Put the alternatives inside one group card. See OR between top-level condition cards.
Which control wins when several match
The extension ranks matching controls in two steps:
- Risk behavior rank. It is fixed, and you cannot change it. Rank 1 is the highest.
- Criticality. Within the same rank, the higher criticality wins: Very High, High, Moderate, Low, Very Low.
If two controls tie on both, the winner is not defined. Give overlapping controls different criticality values.
To find the risk behavior of a use case, see the Use case reference.
For a prompt:
- If a Users Posting Data control applies to the user on that app, the extension applies it, even in Monitor, without checking for sensitive data. Users Leaking Sensitive Data controls do not run there.
- Otherwise, the extension checks the prompt for sensitive data, and criticality decides between the matching Users Leaking Sensitive Data controls.
Do not use both risk behaviors for the same people and apps.
A Monitor control can silence an Enforce control
The extension picks the winner before it looks at the mode. If the winner is in Monitor, the action goes ahead and is only recorded, even when a lower-ranked Enforce control would have blocked it. To make sure an Enforce control applies:
- Give it a higher criticality than every Monitor control of the same rank that matches the same action.
- Narrow or turn off any higher-ranked Monitor control that matches the same action. Criticality cannot overcome rank.
System controls compete too
System controls are ranked like Custom controls. Ten are on by default, all in Monitor. Most match only on Generative AI apps.
For example, a Custom Enforce control on the same use case as Preventing The Leakage Of Sensitive Data Via An AI App needs High or Very High to win. At Moderate the winner is not defined. Below that, the System control wins and users see no popup.
Against a higher-ranked System control, criticality cannot help: narrow or turn off the System control. Tracking Usage Of An Unapproved AI App matches sign-ins and sign-ups (not visits) on unapproved AI apps, so it outranks every password and shared-credential control there. Filter the controls list by Type to see System controls.
Apps you mark Blocked in Inventory are blocked by built-in controls that are hidden from the controls list. They run in every browser at Low criticality and record each visit. Do not add your own control on AI application blocked by organisation or SaaS application blocked by organisation. It cannot block, because these use cases have no Just in Time action. Above Low, it outranks the built-in block and unblocks the users it matches.
What changes the outcome for an app or a person
Most of these settings remove controls before ranking (step 4), so a lower-ranked control can win instead. A reason or acknowledgement given on a popup applies after ranking, to the winner only (step 6).
How prompt frequency affects the result
Prompt frequency, a setting on some Prompt and Justify actions, limits how often the popup appears. For its options, see Conditions and actions. The extension:
- Applies it only to controls on page visits and sign-ins. For other actions, the popup appears every time the control wins.
- Keeps the count per app. Controls with the same risk behavior share one count on that app.
- Counts separately in each browser and each installation.
- Removes a hidden control before ranking (step 4), so a lower-ranked control can win instead.
When nothing matches
If no control matches, or step 4 removed every match, the action goes ahead. The user sees nothing, and no finding names a control. If you expected a control to apply, check that:
- It is enabled, was saved more than 2 minutes ago, and joins its top-level condition cards with AND.
- No Monitor control (System controls included) or Users Posting Data control takes precedence over it.
- Step 4 did not remove it (a turned-off detection, an approved action request or prompt frequency), and the site is not on Whitelist Domain & Pattern.
- An earlier reason or acknowledgement in that tab did not skip the popup.
- The extension is on for the user and has linked the browser to that user. See Extension settings.
- For copied text and file content, the Browser Utility is running on the device. See Content checks need the Browser Utility.
Notes and limits
- Timeouts and offline. If a content check is slow or QuilrAI cannot be reached, the action goes ahead and the content is treated as not sensitive. If the extension cannot download controls, it keeps its last controls. See When a check takes too long and When a browser cannot reach QuilrAI.
- Sign-up forms. While the user types a password on a sign-up form, the extension checks only Unapproved AI Applications Used, Password Reuse, Compromised Password and Weak Password controls, and an Enforce winner shows only a notice. Its own action applies when the user submits the form.
- Change timing. A save takes effect in QuilrAI at once. There are no drafts or versions. Browsers pick up a control change within about 2 minutes, and an app setting or action request decision usually within about 5 minutes. See How long changes take.
- The save check is not a ranking. When you save, the console refuses a control whose conditions are equivalent to another control's in the same use case, including System and turned-off controls. This check ignores rank, mode and criticality. See Resolve a conflict.