Applies to managed Chrome browsers and ChromeOS devices.
As an administrator, you can automatically install web apps for users in your organization. Users can then quickly get to the apps from the launcher on ChromeOS devices or in Chrome browser on other devices.
To make settings for a specific group of users or enrolled Chrome browsers, put the user accounts or browsers in a group or organizational unit. Only user accounts can be added to groups. For details, see Groups and Add an organizational unit.
Step 1: Review policies
Policy | Description and settings |
---|---|
Automatically install specific web apps without user interaction. Users cannot disable or remove them. Unset: No web apps are automatically installed. |
Step 2: Set the policies
Click below for the steps, based on how you want to manage these policies.
Admin console-
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
-
In the Admin console, go to Menu DevicesChromeApps & extensions. The Overview page opens by default.
If you signed up for Chrome Browser Cloud Management, go to Menu Chrome browserApps & extensions.
- Click Users & browsers, Kiosks, or Managed guest sessions.
- (Users only) To apply the setting to a group, do the following:
- Select Groups.
- Select the group to which you want to apply the setting.
- (Optional) To apply the setting to a department or team, at the side, select an organizational unit. Show me how
- (Optional) If you haven’t already, add the web app:
- Point to Add Add by URL .
- Enter the URL.
Use URLs that do not redirect to a different origin. For example, for Google Maps, use https://www.google.com/maps, not https://maps.google.com. - Click Save.
- Go to the app that you want to automatically install.
- Under Installation policy, choose one of the following:
- Force install
- The relevant install and pin option:
- Force install + pin
- Force install + pin to ChromeOS taskbar
- Force install + pin to browser toolbar
- Installed
- Click Save.
Using Group Policy
In the Group Policy Management Editor (Computer or User Configuration folder):
- Go to Policies Administrative Templates Google Google Chrome.
- Open Configure list of force-installed web apps.
Tip: If you don’t see the policy, download the latest policy template. - Enable the policy and enter its compact JavaScript® Object Notation (JSON) data in the text box.
Note: Enter JSON data as a single line with no line breaks. You can use a third-party JSON compression tool to validate policies and compact them into a single line. - Set your desired web app policies:
- Add the URLs of the web apps that you want to automatically install on users’ computers. Use URLs that do not redirect, except to possibly change query parameters. For example, for Google Maps, use https://www.google.com/maps, not https://maps.google.com.
- (Optional) To open URLs in a new tab or window, set default_launch_container to tab or window. By default, web apps open in a new tab.
- (Optional) To create a desktop shortcut, set create_desktop_shortcut to true.
- Deploy the update to your users
The example shows how to:
- Automatically install Google Maps and Google Docs.
- Add a desktop shortcut for Google Maps.
- Open Google Maps in a new window.
- Open Docs in a new tab.
Example JSON data
[
{
"create_desktop_shortcut": true,
"default_launch_container": "window",
"url": "https://www.google.com/maps"
},
{
"default_launch_container": "tab",
"url": "https://www.docs.google.com"
}
]
Compact JSON data
[{"create_desktop_shortcut":true,"default_launch_container":"window","url":"https://www.google.com/maps"},{"default_launch_container":"tab","url":"https://www.docs.google.com"}]
- Add or update the following keys in the <WebAppInstallForceList> key:
- Add the URLs of the web apps that you want to automatically install on users’ computers. Use URLs that do not redirect, except to possibly change query parameters. For example, for Google Maps, use https://www.google.com/maps, not https://maps.google.com.
- (Optional) To open URLs in a new tab or window, set the <default_launch_container> key to <string>value</string>, where value is tab or window. By default, web apps open in a new tab, and the <create_desktop_shortcut> key has no effect on users’ Mac machines.
- Deploy the change to your users.
The example shows how to:
- Automatically install Google Maps and Google Docs.
- Open Google Maps in a new window.
- Open Docs in a new tab.
<key>WebAppInstallForceList</key>
<array>
<dict>
<key>default_launch_container</key>
<string>window</string>
<key>url</key>
<string>https://www.google.com/maps</string>
</dict>
<dict>
<key>default_launch_container</key>
<string>tab</string>
<key>url</key>
<string>https://www.docs.google.com</string>
</dict>
</array>
Using your preferred JSON file editor:
- Go to your /etc/opt/chrome/policies/managed folder.
- Create or update a JSON file.
- For WebAppInstallForceList:
- In url, add the URLs of the web apps that you want to automatically install on users’ computers. Use URLs that do not redirect, except to possibly change query parameters. For example, for Google Maps, use https://www.google.com/maps, not https://maps.google.com.
- (Optional) To open URLs in a new tab or window, set default_launch_container to tab or window. By default, web apps open in a new tab.
- (Optional) To create a desktop shortcut, set create_desktop_shortcut to true.
- Deploy the update to your users.
The example shows how to:
- Automatically install Google Maps and Google Docs.
- Add a desktop shortcut for Google Maps.
- Open Google Maps in a new window.
- Open Docs in a new tab.
WebAppInstallForceList: [
{
"create_desktop_shortcut": true,
"default_launch_container": "window",
"url": "https://www.google.com/maps"
},
{
"default_launch_container": "tab",
"url": "https://www.docs.google.com"
}
]
Step 3: Verify policies on user devices
After you apply any Chrome policies, users need to restart Chrome browser for the settings to take effect. Then, check users’ devices to make sure the policy is correct.
- On a managed device, go to chrome://policy.
- Click Reload policies.
- Check the Show policies with no value set box.
- For WebAppInstallForceList, make sure Status is set to OK and that the policy values match what you set in the policy.
Troubleshoot
If a specified URL fails to load, users see a placeholder app instead of the actual app and app logo. Fixing the issue depends on what’s causing the placeholder app to appear. If the:
- URL redirects to a different origin—You need to edit the URL to use the web app’s final URL after redirection. We recommend that you copy and paste the URL directly from the browser's address bar. For example:
- If you specified example.com and it redirects to www.example.com, you need to change it to www.example.com.
- If you specified http://example.com and it redirects to https://example.com, you need to change it to https://example.com.
- URL redirects to a sign-in page—Users need to open the app, sign in from the redirected page, and close the app again.
- URL can only be accessed on your organization’s network—Users need to connect to the network and then open and close the app or restart Chrome browser or a ChromeOS device.
- URL is temporarily unavailable due to updates or maintenance—Have your users try restarting Chrome browser or a ChromeOS device. If that doesn’t work, when the URL is available again, have them open and close the app again.