After successfully configuring and deploying Workspace ONE Launcher to your fleet of devices, the app is now ready to be used in your organization.

Depending on the device, OS being used, and the version of Workspace ONE Launcher, the profile may require the user to grant app permissions and set Workspace ONE UEM as the default launcher. Granting app permissions allows Workspace ONE UEM console to push launcher settings to control the device, and setting Workspace ONE Launcheras the default overrides the native launcher on the device.

Once users have prepared their devices, they can further customize the layout by adding folders and widgets, and other elements. Admin mode allows users to access higher privileges such as creating shortcuts and other settings in preferences.

Admins set preferences that determine the available customization settings on Launcher devices during Workspace ONE Launcher setup. Settings such as: adding a folder, moving an icon, and swapping the position of an icon, folder or widget can be changed by the end user. View the available preferences in Launcher Device Settings Matrix for Android Deployment and Launcher Device Settings Matrix for Android (Legacy) Deployment.

By default, any changes the user makes to the Workspace ONE Launcher set up, as allowed by the admin in the device preferences, remains on the device in the event the Workspace ONE Launcher is reloaded, admin pushes the profile again, or user exits Launcher. If the admin has to re-push the Workspace ONE Launcher profile that includes changes to the preferences, the new profile overrides any changes the user has made only in the case where the configurations conflict. For example, if the user rearranges the icon on the screen and then the admin has disables that feature in the latest version of the profile, the icons revert to the original position. Another example is if the user has moved around the icons as allowed by the admin and then the admin updates the profile so that there is a different icon in one of the positions, the admins icon will be retained at that position.

Device Requirements

The following tables break down the requirements by Workspace ONE Launcher version and Android OS and also breaks down the requirements by Android setup.

Table 1. Android Requirements
Launcher Version Android 5.0 and Below

Required Additional End User Steps

Android 6.0

Required Additional End User Steps

Workspace ONE Launcher 2.1+(SAFE) No setup required Grant permission required
Workspace ONE Launcher 2.1+ (Non-SAFE) Users have to clear the device's native launcher and set AirWatch as default launcher.

Grant permission required

Users have to clear s native launcher on the device and set AirWatch as the default launcher.

Launcher 2.0.1 & Below-SAFE No setup required Not supported
Launcher 2.0.1 & Below- Non-SAFE No setup required Not supported
Table 2. Android versus Android (Legacy) Setup
Launcher Version Android

Required Additional End User Steps

Android (Legacy)

Required Additional End User Steps

COSU Mode Required Not applied
Default Launcher Automatic

User acceptance required

Notification Access Permission Configurable Configurable
Shared Device Supported Supported
Usage Access Permission Configurable Configurable

Prepare Launcher Devices for Deployment

Once the Workspace ONE Launcher profile is pushed to user devices, users have to grant app permissions which allow the profile to access features on the device and set Workspace ONE Launcher as the default launcher.

  1. Wait for the Workspace ONE LauncherWorkspace ONE Launcher profile to be pushed to device and open the Launcher once installed.
  2. Tap Grant on the "Launcher requires permission" screen.
  3. Toggle Permit Usage access on. Usage access grants the Workspace ONE LauncherWorkspace ONE Launcher app permission to track what other apps are being used, how often, operator, language settings, and additional details.
  4. Navigate to Settings > Launcher > App Info.
  5. Tap Clear Defaults under the "Launch by Default" section.
  6. Tap Workspace ONE Launcher on the Select a Home app prompt.

Using Launcher in Offline Mode

Offline mode is used when devices are being used in check-in check-out mode and allows users to continue their work even when they are unable to log in as themselves or are in areas where network connectivity is unstable.

This setting is applied to both end-users, the staging user, or an organization group that includes both. Assigning to all users ensures the offline mode profile is present when moving between users.

Use the Launcher configuration in the Workspace ONE UEM console to enable offline mode. Once a user attempts to log in and server connection is not detected, they will select Use Offline Mode to continue using Launcher in offline mode. Any changes made while using offline mode are not saved.