Chrome extension deployment using Google Admin Console

After syncing your OUs, you can now deploy the Securly Chrome Extension to your organization. This extension enforces web filtering on Chrome devices, regardless of location.

Before starting the installation process, ensure that your school domain/subdomains are registered with Securly. Our team will initially register the school’s domain. You can then view your registered domains or add more from the Domains tab under Settings.

To deploy the Chrome extension:

1. Login to Google Admin Console.

2. Navigate to Devices > Chrome > Apps and extensions > Users & browsers.

3. Select the OU you want to deploy the extension to and click the "+" button in the bottom right and select "Add Chrome app or extension by ID".

4. Input the extension ID found in the Filter settings page. If you've already deployed the Filter extension you can skip this step. In Filter Settings you'll find the different extension types (Chromebook, Chromebrowser, Edge browser) you'll see the extension ID followed by the custom URL.

5. The installation policy for our extension should be set to "Force install".

6. Click on "Save" in the top right corner.

7. You will then want to modify the update URL at the bottom of the right hand pop out page in extension pushing area. It should say update URL is installation URL.

8. Click "Save" again

This will push the Securly Chrome extension on all Chromebooks, as well as Chrome browsers on Windows and Mac devices belonging to the OU selected (the OUs are user OUs and not device OUs).

Check out our Chrome best practices guide for a detailed look at the recommended settings in the Google Admin Console.

Note

To manage and lock down Windows PCs and browser extensions even when users are not signed into browsers, you must use Intune. Intune will override any extensions managed through Google Admin Console (GAC) and ensures they are pushed to Windows devices regardless of the user's sign-in status.

To force users to use Chrome and ensure they are always signed in, you do not need to use Intune to push extensions. You can continue managing and pushing extensions through GAC, as users will always be signed into Chrome.