Category filter

Configuration profile to disable Incognito mode on macOS devices

Admins may want to disable Incognito mode in Chrome browsers on macOS devices to enforce browsing restrictions, prevent private browsing, or ensure compliance. To disable Incognito mode using the method mentioned below, the Chrome browser on users’ devices must be managed by the organization.

To enroll cloud-managed Chrome browsers, sign up for Chrome Browser Cloud Management (CBCM), generate an enrollment token, and add devices to the console. Once the Chrome browser is managed, admins can deploy a configuration profile using the Deploy Custom Configuration feature to remotely turn off Incognito mode on Macs.


The sample configuration profiles provided below are created using various profile creator applications.

Disable Incognito mode in Chrome browser

To ensure data protection and compliance, you can restrict users from browsing the web in Incognito mode. This can be done by providing the value ‘1’ for the key named IncognitoModeAvailability.

Following are the values either of which can be used for the IncognitoModeAvailability key:

  • 0: Incognito mode available. Users have the option to open webpages in an Incognito window.
  • 1: Incognito mode disabled. Users are unable to open webpages in an Incognito window.
  • 2: Incognito mode forced. Users can only open webpages in an Incognito window.

Below is a sample configuration profile to disable Incognito mode on the user’s device.

Users need to restart the Chrome browser for the configuration profile to take effect.


  • To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
  • Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across devices.
  • Ensure that you do not associate conflicting configurations with the devices.
  • It is recommended to manually validate the configuration profile on a system before executing it in bulk.
  • Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

  • Configuration Profile Repository