Prerequisites and Configuration
Retrieving Extension Policy Information
Retrieve the extension ID and policy contents. In advance, go to Settings > Browser Extension > Browser Extension and copy the values for Extension ID and Extension Policy, then save them.
Forced Installation of the Chrome Extension
The following uses JAMF Pro as an example. Use a configuration profile in your MDM to distribute the forced installation parameter for the Chrome extension. Your environment may already distribute a password manager or similar via a configuration profile. In that case, add the entry to the existing profile rather than creating a duplicate.chrome://policy page.
The extension will be installed automatically. Once installed, you can open the following URL:
chrome-extension://bdeanmdeckegmfjpbnngomallcedjold/options.html
Policy Configuration for the Extension
After distributing the extension, distribute the extension configuration via a configuration profile. Fill inApiKey, CreatedDate, and OrganizationID as constants using the extension policy information retrieved earlier. Set the values for each KEY inside <dict>.
UserEmail is optional but recommended. Distributing a unique value per device or per user allows the server to receive data with identity information rather than anonymized data.
Set a dynamic value for UserEmail.
- JAMF: Use the Payload variable
$EMAIL. - Kandji: Use the Global variable
$EMAIL.
chrome://policy page. (The extension must be installed first.)
If it does not appear, click “Reload policies” once.
chrome-extension://bdeanmdeckegmfjpbnngomallcedjold/options.html.
If your email address and organization ID appear on screen, the setup is complete.
If they do not appear, click the reload button at the bottom right. If that does not resolve the issue, click “Diagnostic Data”, copy the output, and send it to support.
Verifying Operation
The first data transmission begins approximately 30 minutes after setup. Refer to the activity verification guide and confirm that the extension is working correctly.Email Setting Priority
There are three ways to set the Email value. The priority order is as follows:| Priority | Source |
|---|---|
| No.1 | A manually updated email address has the highest priority. An email address set manually in the Extension settings view always takes top priority. |
| No.2 | An email address set via plist is the second priority. Restart the browser or PC after configuring the plist to ensure the value loads reliably. |
| No.3 | The email address used to sign in to the browser is the third priority. If this value loads first, it may take several hours before the No.2 value takes effect. |
How to Remove the Configuration
The following describes how to remove the plist settings configured above.- Updating Chrome’s ExtensionInstallForcelist
- Deleting the extension’s configuration profile
FAQ
Q. Can I use a configuration profile without MDM?
A. This is not currently supported. Due to Chrome extension security restrictions, a manually created plist is loaded at the browser level but cannot be read by the extension.Q. Do I need to set a different EMAIL for each user?
A. Setting a unique email per user is recommended. The extension sends the email address to the server as the “operator” identifier. Any value in email format is technically acceptable. For example, you can use the PC name as the local part (e.g.,HOSTNAME@example.com).
The value appears on the web interface as the sent email address. However, because it may not link to actual users, data such as last-used dates may be harder to use. (It is still sufficient for Shadow IT purposes.)