Category filter

Configuration profile to manage Chrome apps and extensions on Mac

Whether it’s enforcing installation policies or blocking unauthorized extensions, managing Google Chrome apps and extensions allows admins to provide a secure browsing environment for the users. Admins can easily deploy, configure, and update apps and extensions across devices to enhance productivity and enforce security measures for their users.

With the help of Hexnode UEM, you can remotely manage apps and extensions on Chrome browsers for multiple macOS devices by deploying a configuration profile.


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

To manage Chrome apps and extensions 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.

To enforce settings for a particular Chrome app or extension, it is essential to identify the app/extension. Each app and extension available on the Chrome Web Store has a unique identification (ID) that remains the same across different versions.

To locate an app or extension ID:

  • Go to Chrome Web Store.
  • Find and click on the desired app or extension.
  • The app or extension ID can be found at the end of the URL as a 32-character string. For example, ID for Google Docs Offline is ghbmnnjooekpmoecnnnilnnbdlolhkhi.
  • Get the 32-character long ID at the end of the URL

Create a configuration profile that includes all the necessary settings. Use the ExtensionSettings policy to manage extensions in the Chrome browser. With this policy, you can:

  • Set a default policy that applies to all apps and extensions using the * key.
  • Control the installation behavior and permissions of extensions, and customize the settings for individual apps or extensions using their unique app or extension ID.
Configure installation policies for apps and extensions

You can choose to block, allow, automatically install or force install apps and extensions on users’ Chrome browsers.

You can set the installation mode using the following keys:

  • allowed: Users can install apps and extensions from the Chrome Web Store. This is the default key if no installation mode is specified in the profile.
  • blocked: Users are restricted from installing apps or extensions from the Chrome Web Store. A custom error message (up to 1000 characters) can be defined to inform users about the block using the blocked_install_message key.
  • force_installed: Extensions specified in this key are automatically installed without user interaction. Users cannot disable or remove these extensions. The download location for the extensions also needs to be defined.
  • normal_installed: Extensions specified in this key are automatically installed without user interaction. Users have the option to disable these extensions. The download location for the extensions also needs to be defined.

Specify the extension download location


Applies to only force_installed and normal_installed modes.

When you choose to automatically install an extension on devices, you must specify the download location in Chrome within the configuration profile using the update_url key.

Define the extension download location:

  • If the extension is available on the Chrome Web Store, use the URL:
  • If you are hosting the extension on your own server, provide the URL from which Chrome can download the packed extension in the .crx file format.

Block apps and extensions based on permissions

Prevent users from installing apps and extensions that request a specific permission. Specify the permission as the value for the blocked_permissions key.

Refer Chrome app and extension permissions to get a list of permissions that can be blocked from the ‘API’ column in the table provided.

Prevent apps and extensions from modifying webpages

Prevent the extensions from modifying specific websites. It’s important to note that this setting does not limit the installation or removal of extensions.

You can configure the following settings. Along with them, specify the website URLs that you want to prevent the apps and extensions from modifying.

  • runtime_blocked_hosts: Restricts extensions from interacting with the websites specified here.
  • runtime_allowed_hosts: Allows extensions to interact with the specified websites, even if they are listed in runtime_blocked_hosts.

The format of host patterns is [http|https|ftp|*]://[subdomain|*].[hostname|*].[eTLD|*],

The required components are [http|https|ftp|*], [hostname|*], and [eTLD|*], while [subdomain|*] is optional.

Here are a few examples for specifying the host pattern.
Accepted host patterns Matches Doesn’t match
*://* All Urls

Invalid host patterns

  • http://*
  • http://z.*
  • http*://

Sample configuration profile

You can use the Deploy Custom Configuration feature to deploy the below sample configuration profile, which:

  • Blocks all apps and extensions, except for Google Translate (aapbdbdomjkkjkaonfhkkikfgjllcleb).
  • Displays a generic message “This extension is blocked” if the user tries to add blocked extensions. If the user tries to add Google Docs Offline (ghbmnnjooekpmoecnnnilnnbdlolhkhi), they will get the message “Request IT admin to get this extension”.
  • Restricts the extension from accessing webpage.
  • Block all extensions that capture audio directly from microphone.
  • Automatically install Google Keep Chrome extension (lpcaedmchfhocbbapmcbpinfpgnhiddi) without giving users the option to disable it.

Restart Google Chrome on the device for the configurations to take effect.

After associating the configuration profile, you can remotely fetch a list of the installed Google Chrome extensions on the macOS device with the help of a script. Alternatively, you can check the device to ensure that all settings in the profile is applied to its Chrome browser.

Here are the steps to follow:

  1. Open the Chrome browser.
  2. Enter chrome://policy in the URL field.
  3. Click on Reload policies to ensure the latest policies are applied.
  4. Enable the Show policies with no value set option to view all policies.
  5. Verify that the Status is set to OK and confirm that the policy values match the configurations you have set.

View the apps and extension settings configured on Google Chrome


  • 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