For administrators who manage Chrome browser on Windows, Mac, or Linux computers.
As an IT admin for a business or school, you can deploy Chrome browser to users across Microsoft® Windows®, Apple® Mac®, and Linux computers. You can then manage 200+ policies that govern people's use of Chrome, such as the apps and extensions they can use, data security and privacy, their browsing experience, and more.
Get started now
See basic steps for deploying Chrome browser on corporate computers.
Manage policies from: CLOUD WINDOWS MAC LINUX
Manage Chrome policies and extensions from the cloud
Use the cloud-based Google Admin console to:
- Manage Chrome browser across all your corporate Windows, Mac, and Linux computers
- Enforce 100+ machine-level policies that apply whether or not users are signed in to a managed account
- Easily install and block Chrome apps and extensions
- View reports listing browser versions, installed apps and extensions, and enforced policies
- Enforce user-level policies that apply when users sign in to a managed Google Account on any device
Sign up and get started: Set up Chrome browser Cloud Management
Manage policies with on-premise tools
Install MSI (Windows) and policy templates
Chrome Enterprise provides all the files you need to install and manage Chrome browsers on corporate devices (Windows, Mac, and Linux):
- Microsoft Installer (MSI) for installing Chrome browser on managed Windows computers
- Administrative templates for configuring corporate policies on managed PCs (Windows, Mac, Linux)
Get the files: Chrome Enterprise Bundle | What's in the bundle?
Enforce policies on-premise
After Chrome browser is installed on your users’ computers, use your preferred on-premise tools to enforce policies that control their use of Chrome. Policies can apply whether or not people are using Chrome browser or signed in to any account. You can enforce policies that users cannot modify. Or set default preferences that users can change.
- Enforce policies using Windows Group Policy or your preferred tool for Mac configuration files or JSON files.
- Alternately enforce policies by updating the Windows Registry.
- Deploy default user preferences using the initial_preferences file.
Note: For Chrome browser 91 or later, the file named initial_preferences replaces the master_preferences file. To minimize any disruption, Chrome continues to support both filenames, and more notice will be given in the Chrome Enterprise release notes before we remove support for the former filename.
Support legacy browser apps
Your organization can take advantage of Chrome browser while still easily accessing older websites and apps that require Internet Explorer. Just deploy Legacy Browser Support (LBS). When users click links in the Chrome browser that instead require a legacy browser, the URL automatically opens in the legacy browser.