The Linux Google Chrome Extension Deployment and Blocking Policy lets administrators enable the Swif Chrome extension, automatically install required extensions, and block specific extensions on enrolled Linux devices.

The policy is delivered through the Swif agent and supports both company-owned and BYOD devices. Use it to provide approved browser tools and prevent unwanted extensions from running.

The current policy includes three settings:

This policy manages extensions. Install Google Chrome separately if it is not already available.

The policy definition does not specify a distribution, architecture, or minimum Linux version. Verify compatibility with your Linux distribution and Chrome installation before broad deployment. Support for Google Chrome does not automatically establish support for Chromium, Brave, or other Chromium-based browsers, or for alternative packaging methods.

Enables the Swif Chrome extension on the device.

Turn this setting on when the deployment requires the Swif extension. After the policy applies, confirm that the extension appears in Chrome.

When changing this setting from On to Off, verify the resulting extension state. The setting's default alone does not establish whether an existing installation will be disabled or removed.

Specifies extensions to install silently, without user interaction. While the force-install requirement applies, users cannot disable or uninstall these extensions through Chrome.

Add one extension ID per list entry. Enter the ID itself, rather than the extension's name or full Chrome Web Store URL.

Review the publisher, permissions, and business purpose before requiring an extension. Force-installed extensions receive permissions without the usual user approval prompt. Google: Automatically install apps and extensions

Specifies extensions that users cannot install. When a listed extension is already installed, it is disabled after the blocking policy takes effect. Users cannot re-enable it while the block applies.

Add one extension ID per list entry. Blocking an extension should not be described as deleting its files or stored data.

Keep the install and block lists consistent. Google's ExtensionInstallForcelist takes precedence over ExtensionInstallBlocklist, so an extension required by a force-install policy may remain installed despite a blocklist entry. Resolve any conflicting requirements before deployment. Google: Force-install policy definition

To obtain an ID from the Chrome Web Store:

For an installed extension, open chrome://extensions and enable Developer mode to display its ID. Turn Developer mode off afterward if it is no longer needed. Google: Linux extension policy setup, Google: Force-install policy definition

Use real IDs from the extensions you intend to manage. Example placeholders are not deployable extensions.

An offline device must reconnect to receive changes. Receiving the policy and downloading an extension are separate steps; confirm both before considering deployment complete.

Use the actual extension IDs for the tools your organization has selected.

The install list is a list of required extensions, not an exclusive allowlist. Adding IDs to it does not block all other extensions. The current policy does not expose a separate list of extensions users may optionally install.

After the policy reaches a test device:

Close and reopen Chrome if the expected changes are not visible after refreshing policies. Use the policy source and scope to compare behavior across affected users or profiles. Google: View a device's current Chrome policies

Google Chrome's standard Linux directory for mandatory platform policies is:

Google documents JSON policy files in this directory. Files should be protected from modification by non-administrators. Conflicting values for the same policy in multiple files can produce undefined behavior. Google: Set policies on Linux

This is a Chrome policy location, not a documented Swif-specific filename. For diagnosis, you can list its files:

Review other configuration-management tools, provisioning scripts, and Chrome cloud policies when troubleshooting. Avoid adding a second JSON file to override a Swif-managed value; resolve the conflict at its source.

For BYOD devices, check the effective policy scope before deployment. A personal Google account does not by itself isolate a browser from machine-level policies. Google: View a device's current Chrome policies

Check that:

If the browser is packaged differently or runs in a sandbox, verify that it can access the relevant host policy files. Do not assume that a successful Swif policy report confirms compatibility with every browser package.

Check whether another policy force-installs the extension. Also inspect ExtensionSettings, which Google documents as overriding older extension policies, including the force-install and blocklist policies. Google: Linux extension policy setup

Remove conflicting configuration, let the device check in, and refresh Chrome policies. Confirm the extension's actual state afterward.

Review other Swif assignments, provisioning scripts, local Chrome policy files, and Chrome cloud management. Configure each setting through one authoritative source where possible.

The documented Swif fields accept extension ID lists and do not expose a separate custom update URL. Google's support for self-hosted extension delivery does not establish that this Swif policy supports that workflow. Contact Swif Support before using it to deploy extensions outside the Chrome Web Store.

Include the device identifier, Linux distribution, Chrome version and installation method, policy status, affected extension IDs, and relevant errors from chrome://policy.

Edit the extension lists, save the policy, and allow the device to check in. To stop assigning the configuration, remove its assignment and verify the resulting Chrome policies.

Changing a force-install list can remove extensions: Google documents that an extension removed from the effective ExtensionInstallForcelist is automatically uninstalled. Test changes before broad deployment. Google: Force-install policy definition

Other management sources may continue to require or block an extension after a Swif policy changes. Check both chrome://policy and chrome://extensions to confirm the final result.