Limits and browser differences
Updated on 10 November 2026.
The Browser Extension applies most controls the same way in every browser. This page lists the exceptions and limits. You create Browser Extension controls under Govern > Policy Engine > Endpoint Agent > Browser (see Browser controls).
Key terms
What each browser supports
The extension has separate builds for Chromium-based browsers (Chrome, Edge and others), Firefox, and Safari on macOS. All builds check the same activity and run controls the same way, except an Enforce control with no Just in Time action.
Enforce controls without a Just in Time action
Only a Just in Time action can act in the browser, so an Enforce control with only Remediation Action or Activate Agent actions never shows a popup, and the user's activity goes ahead:
- Chromium-based browsers and Firefox run the control as Monitor. They record the match as a finding in Findings & Interactions, so the follow-up actions run.
- Safari runs the control as saved and records nothing, so the follow-up actions never run.
Give every Enforce control a Just in Time action. To only record activity, use Monitor mode, which records the same way in every browser but does not run Activate Agent.
Content checks need the Browser Utility
The extension cannot read the clipboard or local files itself. Without a running Browser Utility:
- Conditions on copied content or on Copied From Process (the desktop app the text came from) cannot match. Controls that act on any copy or paste still work.
- Copy controls still show their popup, but a block does not clear the clipboard, and a request for a reason does not lock pastes. With the Browser Utility, pastes are blocked in every tab until the user gives a reason, and closing the popup clears the clipboard.
- An upload control that checks file content lets the upload continue unscanned after about 3 seconds.
Deploy the Browser Utility to every device that needs content checks. In Observe > Users > Browser deployment, a Utility value of Not connected or Off means content checks do not run for that user. The column appears only with a Browser Utility license. See Clipboard monitoring, File indexing and Validate the deployment.
Controls that do not run as saved
The console saves these controls without a warning.
OR between top-level condition cards
Every browser ignores a control whose top-level condition cards are joined by OR. The control shows as on, but never acts or creates a finding. Put the alternatives in one Group condition instead:
- In Add to this control, select Add condition and fill in the first condition.
- On that card, select Add condition to group. The button appears once the condition is complete. The card becomes a Group condition with a second row.
- Set the second row's AND / OR menu to OR, then fill in the row.
- Keep the menu between top-level cards at AND.
To match several values of one attribute, use is in, for example Name is in ChatGPT, Gemini. Each attribute can be used only once in a control's additional conditions, except URL.
Other controls that run differently
- A group matches more than its wording suggests. Rows are read top to bottom, and AND does not take precedence over OR: "A AND B OR C" means "(A AND B) OR C". Use only AND or only OR inside a group. See How conditions combine.
- Prompt frequency works only on visit and sign-in controls. The console also offers it on other Just in Time actions, but there the popup appears every time. See How controls are evaluated.
- An Enforce control matches but shows no popup. When several controls match, only one applies. If that control is in Monitor, the action is only recorded. A Monitor control can win, for example a System control, or, in Chromium-based browsers and Firefox, an Enforce control with no Just in Time action. Avoid overlapping Monitor and Enforce controls. See A Monitor control can silence an Enforce control and System controls compete too.
- A control skips one person or one app. A detection turned off for the app, or an action request approved for that person, leaves the control out of evaluation. A person's own access or approval value replaces the organization's value. Check the app's Controls & configuration in Inventory and approvals in Action requests. See What changes the outcome for an app or a person.
How long changes take
The banner Saves apply immediately. means the change is saved in QuilrAI at once, because Browser Extension controls have no drafts or versions. Each open, online browser applies it the next time it checks in:
The extension reuses a scan result for the same text for 5 minutes. After you change a detection model, retest with different text or wait 5 minutes.
When a check takes too long
If a scan does not answer in time, the action fails open: it continues as if it contained no sensitive data.
An upload is held only when a matching control could block it or ask for a reason. During the scan, a Scanning your files popup blocks the page. Closing the tab cancels the upload.
Archives with password-protected entries or over size or nesting limits, and unreadable file types, do not fail open: upload controls that act on sensitive data act on them. A password-protected file matches the Encrypted condition instead. If users must upload such files, narrow the control with a condition such as Smart Group, or approve their action requests.
When a browser cannot reach QuilrAI
Activity records that fail to send are dropped after 5 retries or 24 hours, so a device that stays offline for long can leave gaps in Findings & Interactions.
Other behavior to plan for
- Restored controls come back off. When you save a control whose conditions match a deleted control, the Control already exists dialog offers Restore existing. The restored control is turned off. Turn on its Status. See Resolve a conflict.
- The Endpoint Agent Policy Engine does not affect Browser controls. Its on, off and pause actions, on Govern > Policy Engine > Endpoint Agent > Desktop, apply only to Endpoint Agent devices. To stop Browser controls, turn them off, or turn off the extension in Settings > Browser Extension. See Turn on, turn off and pause.
- A device can be checked by both products. If the Endpoint Agent also monitors the browser, both can check the same prompt, each with its own popup and finding. To avoid this, turn that browser off for the app under Application Monitoring in Settings > Endpoint Agent. See Limits and behavior to know.
- Email controls cover Gmail only. To control other webmail sites, create a control on A user is visiting an application with a Domain or Name condition and a block or justify action.
- Some sign-ins always show an account chooser. In Chromium-based browsers, signing in to ChatGPT with Google, or to Microsoft Copilot or Microsoft 365 with a Microsoft account, always shows the account chooser, even without sign-in controls, so the extension can see the account. Tell users to expect it.