Deploy the extension with the Google Admin console
Force-install the Sorvek extension in Chrome through the Google Admin console, then enroll each device in your Sorvek organization.
On this page
The Google Admin console can force-install the Sorvek Discovery extension in the Chrome browsers it manages, using the ID of the Sorvek listing on the Chrome Web Store. The device is then enrolled in your Sorvek organization when the employee signs in with Microsoft. Sorvek does not provide a managed configuration template for the Google console, because this configuration must carry each person's address.
What the Google console covers
The Google console manages Chrome: browsers enrolled in Chrome Enterprise Core (formerly Chrome Browser Cloud Management) and Chrome profiles signed in with a managed account, depending on your organization. It does not manage Edge. For Edge, see Deploy the extension with Microsoft Intune.
Values to use
| Item | Value |
|---|---|
| Extension ID | Shown in the Sorvek console: Settings > Browser extension, Deployment section |
| Chrome Web Store update URL | https://clients2.google.com/service/update2/crx |
| Self-hosted package ID (existing installations only) | Shown in the same place in the console |
Step 1: force-install the extension
The labels below are Google's and may change. The Sorvek console links to Google's documentation (https://support.google.com/chrome/a/answer/6306504).
- In the Google Admin console, open the Chrome apps and extensions settings.
- Choose the target organizational unit.
- Add a Chrome app "by ID" with the extension ID shown in the Sorvek console (Settings > Browser extension, Deployment section).
- Set its installation mode to "Force install".
- Save.
Self-hosted variant (CRX package signed with the Sorvek key, served by your own update.xml): add the app from a custom URL, with the self-hosted package ID shown in the Sorvek console and the URL of your update.xml.
Step 2: enroll the devices
Once installed, the extension does not open any page. Each employee:
- Clicks the Sorvek icon in the browser toolbar. The window shows Not connected.
- Clicks Sign in with Microsoft and chooses their Microsoft work account.
- If your organization leaves a feature optional, confirms their choices with Confirm my choices (or Decline all). If the features are required or disabled, the extension activates without a choice page.
The sign-in succeeds only if the Microsoft account belongs to the Microsoft tenant linked to your Sorvek organization, and if the SaaS Discovery module is active. The error messages are described in Troubleshoot the extension.
If you push a managed configuration
An extension policy set in the Google console applies to the whole target organizational unit or group. It is therefore not suited to user_email, which must contain each person's address.
Managed configuration keys accepted by the extension:
| Key | Content |
|---|---|
user_email |
The person's work address, known to the directory that Sorvek syncs |
deployment_key |
Your organization's deployment key (letters, digits, _ and -, at least 16 characters) |
browser_product |
Optional. The declared browser, when automatic detection is not enough (for example Dia or Opera Neon) |
The deployment key is generated in Settings > Browser extension, Deployment section, Chrome / Edge card, with Generate deployment key.
Check on a pilot device
- Open
chrome://policy: the installation policy must list the extension ID. - Open
chrome://extensions: Sorvek Discovery must appear with this ID. - After the employee signs in, in the Sorvek console, in the Installations table on the Browser extension page: a row with their address, the Active status and the enrollment "Microsoft sign-in".
Can’t find your answer?
Already a customer? The support bubble at the bottom of the app sends your question with its context. Otherwise, write to the Sorvek team.