Skip to main content

Deploy Anzenna Chrome Extension via Google Admin Console

This guide walks you through deploying the Anzenna Chrome Extension to all users in your organization using the Google Admin Console.

Prerequisites​

  • Google Workspace Super Admin access
  • Anzenna account with integration access
  • Chrome Browser Cloud Management enabled

Step-by-Step Instructions​

Part 1: Configure Extension in Google Admin Console​

  1. Navigate to admin.google.com

  2. From the main menu, select Chrome browser

  3. Click on Apps & extensions

  4. Click Add Chrome app or extension by ID

  5. Enter the Anzenna Extension ID: 

     dfgkggkanghelhmebphoccfhkbjcgjoh

  6. Select From a custom URL as the installation method

  7. Paste the manifest URL: 

     https://img.anzenna.ai/extensions/anzenna/manifest.xml

  8. Click SAVE to apply initial settings

  9. Enable Force install for the extension across your organization

Part 2: Configure Anzenna Policy​

  1. Log into Anzenna

  2. Navigate to Settings > Integrations

  3. Find the Google Workspace integration card
  4. Copy the JSON policy value displayed in the integration settings
Token Purpose

The token in the policy is an identifier only – it's not a security credential.

  1. Return to the Google Admin Console Apps & extensions page

  2. Click on the Anzenna extension to edit its settings

  3. Under Policy for Extensions, paste the JSON policy you copied from Anzenna

  4. Set the Installation URL to: 

     https://img.anzenna.ai/extensions/anzenna/manifest.xml
  5. Click SAVE to apply these settings

  6. Reopen the extension settings and verify the Update URL from the extension manifest. This field only appears after the initial save.

  7. Click SAVE to finalize all configurations
Deployment Timeline

The Chrome extension will be installed organization-wide within the next
24 hours as devices sync with Google Admin policies.

Part 3: Enable Monitoring in Anzenna​

  1. In the Anzenna application, go to Settings

  2. Click on Preferences

  3. Enable data exfiltration or shadow IT tracking for the browser extension

Restrict Installation to Corporate Profiles Only​

The steps above install the extension for every managed user. If you also manage enrolled browsers through Chrome Browser Cloud Management (for example, an enrollment token pushed by your MDM), a force install applies at the browser level and lands in every Chrome profile on the device — including personal profiles. Use the steps below to install the extension only on the corporate (managed Workspace) profile.

Two enforcement levels

Chrome policy reaches a device two ways. A user policy follows the signed-in corporate Google account into its profile and never touches a personal profile. A browser policy (Chrome Browser Cloud Management) applies to the whole browser regardless of who is signed in — every profile. Corporate-profile-only means deploying at the user level and keeping the extension off the browser level.

Separate browsers and users into different OUs​

  1. Place your enrolled browsers in one organizational unit (for example, your top-level OU). Enrolled browsers join an OU based on the enrollment token used, and you can move them under Devices > Chrome > Managed browsers.
  2. Place your users in a separate child OU (for example, Staff).
Why separate them

A browser's policy comes from the OU the browser is enrolled in; a user's policy comes from the OU the user is in. Keeping them in different OUs lets you force install for users without forcing it onto the browser (all profiles).

Force install on the user OU only​

  1. Go to Chrome browser > Apps & extensions > Users & browsers.
  2. Select your user OU (for example, Staff) and set the Anzenna extension to Force install, following Part 1 of the main instructions above.
  3. Select your browser OU (the one your enrolled browsers are in) and make sure the Anzenna extension is not force installed there — set it to Allow install or leave it unconfigured. This is what keeps it out of personal profiles.

Merge force-install lists​

If you force install any other extension at the browser level (for example, Chrome Reporting or Endpoint Verification), Chrome lets the browser-level list override your user-level force install, and the Anzenna extension will not install at all. Enable list merging so the two lists combine instead of one replacing the other.

  1. Select your browser OU.

  2. Set the PolicyListMultipleSourceMergeList policy to include only the force-install list:

    ["ExtensionInstallForcelist"]
  3. Save, then fully quit and relaunch Chrome on a test device.
Set this on the browser OU, not the user OU

PolicyListMultipleSourceMergeList only takes effect as a browser (machine) policy. If you set it on the user OU it is ignored. Apply it to the OU your enrolled browsers are in — the same OU where you left the extension un-forced in the previous step. Scoping it to only ExtensionInstallForcelist leaves every other policy on its normal precedence.

Verify​

  1. On the corporate profile, open chrome://policy and click Reload policies.
  2. Find ExtensionInstallForcelist. The effective value should list the Anzenna extension ID (dfgkggkanghelhmebphoccfhkbjcgjoh) with no Conflict warning.
  3. Open a personal Chrome profile on the same device and confirm the extension is not installed.
Requires corporate sign-in

A user-level policy only applies when the person is signed into Chrome with their corporate Google Workspace account. A signed-out or personal profile will not receive the extension — which is exactly the intended behavior here.

Need help? Contact

Anzenna Support

for assistance.