Deploy the browser extension

Before you begin

Use the Deployment Center in elba for the current configuration values, installation links, and downloadable artifacts for your workspace. Do not reuse identifiers, policy values, or scripts copied from another environment or an earlier rollout.

You will need:

• Access to Browser Security settings in elba.
• Administrative access to the browser or device-management platform you plan to use.
• A defined pilot group and target device scope.
• A communication plan for any users who must sign in or install manually.

Choose a deployment method

The methods shown in elba vary by browser and platform. Select a browser in the Deployment Center to see the options and exact values available for it.

Standard rollout process

1. In elba, open Browser Security settings and select the deployment view.
2. Choose the target browser and deployment method.
3. Copy the displayed values or download the provided artifacts.
4. Apply them in your browser, device-management, or RMM platform.
5. Assign the policy to the pilot group and trigger a policy refresh where appropriate.
6. Restart or relaunch the browser if the management platform requires it.
7. Confirm the policy and extension state on a pilot device.
8. Ask the pilot user to sign in to the extension.
9. Verify the user's extension status in elba before expanding the assignment.

Method-specific guidance

Google Admin

1. Open the Chrome application and extension management area in Google Admin.
2. Select the target organizational unit.
3. Add the extension using the values displayed in elba.
4. Set the installation policy for the target users or devices.
5. Apply the optional advanced policy value only if it is part of your browser-management model.
6. Refresh policy and validate the extension on a managed device.

Microsoft Intune

1. Create or update the browser policy for the target Windows devices.
2. Add the setting described in the elba Deployment Center.
3. Paste the generated name, configuration location, and value exactly as displayed.
4. Assign the policy to the pilot device group and trigger a sync.
5. Confirm that the browser reports the policy and installs the extension.

Group Policy

1. Open Group Policy Management and edit the target computer policy.
2. Apply the browser extension policy values generated by elba.
3. Preserve existing settings for other managed extensions when merging policy values.
4. Wait for the normal policy refresh or trigger one according to your standard process.
5. Relaunch the browser and validate the resulting policy state.

macOS MDM

1. Create a macOS configuration profile for managed Chrome preferences.
2. Use the preference domain and configuration values displayed in elba.
3. Assign the profile to the pilot Mac group.
4. Wait for device check-in, then relaunch Chrome if necessary.
5. Confirm that the managed preference and extension are present.

RMM

1. Download the installation script from elba.
2. Run it through your RMM platform with the administrative context required by that platform.
3. Keep the downloaded script unchanged so its installation and verification behavior remains intact.
4. Retain the matching rollback script with the deployment record.
5. Review the script result and validate the extension on a pilot endpoint.

Manual installation

Use manual installation for a pilot or when centralized browser management is unavailable. Share the installation link shown in elba, then ask the user to install the extension and sign in. Track completion from the deployment view and send a reminder if needed.

Validate the deployment

On each representative platform, confirm that:

• The browser's policy page shows the expected managed extension policy where applicable.
• The extension is installed and managed as intended.
• Existing policies for unrelated extensions remain intact.
• The user can open the extension and sign in successfully.
• The user's extension status appears correctly in elba.
• The Browser Security capabilities you intend to use behave as expected in your test scope.

If a status does not update immediately, refresh device policy, relaunch the browser, and confirm that the extension has an active connection to elba.

Roll back safely

Plan rollback before broad assignment.

1. Remove or unassign the browser or device policy from the affected group.
2. For script-based deployment, use the matching rollback artifact supplied by elba.
3. Remove only the elba extension entry when the policy also manages other extensions.
4. Refresh policy and relaunch the browser.
5. Confirm that the managed policy and extension state match the intended rollback outcome.

For product context, read Browser extension and Browser extension capabilities. For unresolved installation or sign-in issues, continue to Troubleshooting.