How to Configure the Zoom for Chrome PWA

This post was most recently updated on July 28th, 2022

In case you’re an administrator who manages Chrome apps, you can use the Google Admin Console to configure Zoom for Chrome PWA. This gives you the capability to deploy your PWA to your users with exactly the policies you want in terms of deployment and configuration.

Upon implementing Zoom for Chrome PWAs, please refer to the getting started guide for detailed guidance on how to use the Zoom for Chrome PWAs once they have been implemented.


By June 2022, ChromeOS apps will no longer be supported across all operating systems, so Zoom for Chrome PWA will be the replacement for it. For the smooth transition from the ChromeOS app to the new Zoom for Chrome PWA, admins are strongly recommended to begin migrating users.

Prerequisites for configuring Zoom for Chrome PWA

  • It is possible to access the Google Admin console via the web browser
  • Using Chrome OS version 93 or higher

Supported policies

Installation Policies

Install Zoom for Chrome PWA in accordance with the following policies:

Parameter Value Type Description
Force Install Boolean Installs the app automatically and prevents usersFrom removing it.
Force install + pin Boolean Installs the app automatically and prevents users from removing it. On a Chrome OS device, this pins the app to the taskbar.
Allow install Boolean Lets users install the app.

Zoom for Chrome policies

When using Zoom for Chrome PWA, you may specify any of the following parameters. If you do not specify any parameters, the default value will be used.

Parameter Value Type Default Description
BlockUntrustedSSLCert Boolean False Specify if the app will stop for an invalid certificate. If false, then the user will be prompted to trust the certificate or not.
DisableGoogleLogin Boolean False Specify if signing in with Google is disabled.
DisableFacebookLogin Boolean False Specify if signing in with Facebook is disabled.
DisableLoginWithSSO Boolean False Specify if signing in with SSO is disabled.
DisableLoginWithEmail Boolean False Specify if signing in with email is disabled.
SetSSOURL String (empty) Predefine the vanity URL used to log in using SSO.Example: Enter “success” to set the SSO URL as
ForceLoginWithSSO Boolean False Specify if SSO is the default login method. If set to true, users can still switch to other login methods. This item will not apply if DisableLoginWithSSO is set to True.
SetAccountIDsRestrictedToJoin String (empty) Set account IDs* that the client is restricted to join meetings hosted by specific accounts
AutoLoginWithChromeBookUserAccount Boolean False Direct Chromebook users automatically to the Google Authentication page, where they can select their saved Google credentials.
This does not apply if DisableGoogleLogin is set to True.
GoogleLoginRenameDisabled Boolean False Prevent users from renaming before joining a meeting if signed in via Google
SSOLoginRenameDisabled Boolean False Prevent users from renaming before joining a meeting if signed in via SSO


In order to receive your username and account ID, the account owner or admin will need to get in touch with Support and tell them what you need.

How to configure Zoom for Chrome PWA

  1. Access the Google admin console by logging into your Google account.
  2. Select Chrome under Devices from your Home page.
  3. Go to Applications & extensions.
  4. To configure an app, select Users & browsers.
  5. By leaving the top organizational unit selected, the setting will be applied to all users. If you choose another organizational unit in your organization, the setting will only apply to it.
  6. Simply click the Add by URL button located in the bottom right hand corner.
  7. You can also open PWA by entering the URL ( and selecting how you would like it to open.
  8. Then click Save.
  9. If you have an app policy file that you wish to upload, you can do it manually.
  10. Click the Save button.

Check to see if the configuration was applied correctly:

  1. Chrome users should enter chrome://policy in their browser.
  2. You may expand the ManagedConfigurationPerOrigin policy value by clicking Show more and finding the managed configuration per origin policy section.
  3. In your browser, copy the value of managed_configuration_url, load that page, and then validate that the JSON is the same.

Sample JSON

In the following example, we will show you what it looks like to disable Google login and predefine the vanity URL to be used to log in through SSO.

 "DisableGoogleLogin": true,

 "SetSSOURL": "success" 

Note: Just the domain is necessary when setting up the SSO URL. The full SSO URL does not need to be used, such as