Skip to main content
The VisIQ browser extension does not run in Chrome Incognito, Edge InPrivate or Guest windows. On a Mac with the sensor installed, the sensor governs AI traffic in those windows instead, for as long as one is open. To do that it asks Chrome and Edge which of their windows are private, and macOS allows that only with an Automation permission. Deploy the profile below from your MDM and the permission is granted on every Mac, with no prompt to the user.

Deploy the profile

1

Save the profile

Copy the profile at the end of this page and save it as VisIQ-Private-Windows-Automation.mobileconfig.
2

Upload it to your MDM as a custom configuration profile

  • Jamf Pro: Computers, then Configuration Profiles, then Upload.
  • Microsoft Intune: Devices, then macOS, then Configuration, then Create, then New policy; choose Templates, then Custom, set the deployment channel to Device channel, and upload the file.
  • Kandji: Library, then Add new, then Custom Profile.
3

Assign it to the same Macs as the sensor

Use the same group or scope you use for the VisIQ sensor. The permission applies at the profile’s next check-in; nothing restarts.
A Privacy Preferences profile installs only from an MDM. Opening the file on a Mac does not grant the permission.

What the profile allows

It lets one program, the VisIQ sensor at /usr/local/bin/visiq-discovery signed by VisIQ Labs, send Apple Events to Google Chrome and Microsoft Edge. The sensor uses them for one thing: reading whether each window is normal or private. It does not read titles, addresses, tabs or page content. Without the profile, the sensor does not govern private windows on that Mac. Normal windows are still governed by the extension.

The profile

VisIQ-Private-Windows-Automation.mobileconfig