Anything left off the list will not be installed. Note that whatever you want to allow must be included in the list. Extensions, themes, user scripts, hosted applications, legacy packaged applications and platform applications are the values that are supported. This setting overrides the extension block list policy, and the extension can’t be disabled on uninstalled.Įxtension Allowed Types: Here you can create a list of what types of extensions and apps you will allow to be installed. So lets touch on management through those methods, for organizations that haven’t quite made the move to Chrome Browser Cloud Management yet.įor starters, here are some of the most used options for managing extensions (some also apply to apps) via Windows Group Policy or via Plists on Macs: Installing or allowing extensionsĮxtension Install Allow List: These are the extensions that you have approved to be installed within your environment.Įxtension Install Force List: This will install the extension in the managed instance of Chrome. However, some enterprises may need to still use Group Policy on Windows or plists on Mac to manage extensions. In an earlier post in this series, we’ve detailed how Chrome Browser Cloud Management is the easiest way to audit installed extensions and manage them.
However, some extensions can have the potential for far reaching rights to sites your users visit and devices they browse from, giving IT the desire to closely manage which extensions are in their environment and how they behave. Extensions themselves are a great tool for productivity and customization of Chrome. Many enterprises are looking to better manage extensions on their corporate devices.
0 kommentar(er)
