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.
The following tables break down the requirements by Workspace ONE Launcher version and Android OS and also breaks down the requirements by Android setup.
|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|
Android versus Android(Legacy) Setup
|Launcher Version||Android Required Additional End User Steps||Android (Legacy)Required Additional End User Step|
|COSU Mode||Configurable||Not applied|
|Default Launcher||Automatic||User acceptance required|
|Notification Access Permission||Configurable||Configurable|
|Usage Access Permission||Configurable||Configurable|
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.
Offline mode is a Launcher profile you can configure for multi-staging users in order to access apps within Launcher without the user having to checkout when a device is unable to connect to the server. When a user tries to authenticate with their valid credentials but the device is unable to communicate with the server, an additional page displays asking the user if they want to continue using the device in offline mode. This page is only displayed when offline mode is turned on and the Launcher profile is present in Hub when the device is on the Login screen.
Administrators have the ability to restrict access to offline mode by protecting it with a PIN or a Password. When the user selects Offline mode, they might be required to authenticate using their pin or password if it is configured in the offline mode Launcher profile. Upon successful authentication, users can access the apps that are added to the allow list within the canvas. A banner is displayed to the user indicating that Launcher is currently running in Offline mode.
In offline mode, user details are not updated on the console because of server authentication failure. The console continues to show the staging user as the current user. In order to return to the login screen, the user selects the reconnect button on the Offline Mode banner at the top of the screen. This tries to connect the device to the server. If the server connection is established and users see a Good server Connection message, then the user needs to choose whether they want to login or continue using Launcher in offline mode.
Offline Mode is turned on while configuring the Launcher profile. The initial steps can be found in the Configure Workspace ONE Launcher Profile
Once you get to step 6 in the setup, follow these steps to turn on Offline Mode:
Once the device is enrolled into Work Managed Mode and the user attempts to log in, they are prompted with Use Offline Mode message that lets them know there is no server connection. To continue, the user selects Use Offline Mode and enters the pin or passcode set in the console. A banner is displayed indicating that the device is being used in offline mode.
Once finished with the device, the user returns to the check-in check-out screen by selecting Reconnect which logs the device and clears the app data for that user. The device is returned to the login screen and ready for the next user.
Guest mode is a Launcher profile configured for multi-staging users in order to access apps within Launcher without the user checking out the device. This profile option is ideal for when a device needs to be used by anyone who does not have login credentials or is not part of your organization
When user selects to use Guest mode, they might be required to authenticate using PIN or Password if it is configured in the Guest mode Launcher profile. Upon successful authentication, guest users can access the apps that are allow listed within the canvas. A banner is displayed to the user indicating that Launcher is currently running in Guest mode.
There is no user based authentication happening to access guest mode, so user details are not updated on the console. The console continues to show the current user as Staging user.
Guest Mode is turned on while configuring the Launcher profile. The initial steps can be found in the Configure Workspace ONE Launcher Profile
Once you get to step 6 in the setup, follow these steps to turn on Guest Mode:
Once the device is enrolled into Work Managed Mode and the user attempts to log in, the user selects Use Offline Mode and enters the pin or passcode set in the console. A banner is displayed indicating that the device is being used in guest mode. The user now has access to features turned on the in console.
Once finished with the device, the user returns to the check-in check-out screen by selecting Log in which logs the device and clears the device data for that user. The device is returned to the login screen and ready for the next user.
Users cannot view the status bar or Workspace ONE Launcher action bar on their device when devices are locked into Template mode. Users can swipe down the screen to display the status bar.
Navigate to Devices > Profiles > List view > Add > Add Profile > Android > Device > Launcher > Configure > Template Mode.
Select Preferencesand enable Allow Status Bar and Allow Mini Launcher Bar.
Notifications for different applications display inside Workspace ONE Launcher.
Available notifications display as an alert on the Options menu.
Tap the alert.
View notifications from the Options menu.
Open the specified app by tapping the notification.
Ghost Icons are placeholder icons for apps that are whitelisted for user but are not installed on the device.
In the Workspace ONE UEM console you may have whitelisted ten applications but only five are installed on the device. Users can see icon placeholders for the apps that are not installed. Depending on the app mode that has been configured, the behavior of the ghost icons vary:
|Single App Mode||For public applications, users tap the icon and are redirected to the Google Play Store to download the app.For internal application, users tap the icon and are redirected to the AirWatch Catalog too download the app.|
|Multi App Mode||For public applications, users tap the icon and are directed to the Google Play store to download the app.|
|On Demand||Ghost icon displays on device until user taps itto start download.|
|Auto Push||Ghost icon will display on device and app is automatically installed as the Launcher profile is deployed to devices.|
Even if the Play Store has not been whitelisted in the Workspace ONE UEM console , it is temporarily whitelisted to allow the users to download the app. Once downloaded, the app appears and is ready for use.
Users can access native device settings from the Options menu and adjust them according to their business needs.
|Sound||Adjust the volume levels.|
|Display||Adjust brightness and set sleep timer.|
|Wi-Fi||Connect the device to a Wi-Fi network.|
|Cellular Data||Enable the use of network data over Wi-Fi. Not available while running Workspace ONE Launcher on Android 5.0 devices.|
|Bluetooth||Pair a Bluetooth device. Not available while running Workspace ONE Launcher on Android 5.0 devices.|
|Location||Enable GPS services. Not available while running Workspace ONE Launcher on Android 5.0 devices.|
|Security||Set device administrator settings. Not available while running Workspace ONE Launcher on Android 5.0 devices.|
|Language||Determine the language and input options. Not available while running Workspace ONE Launcher on Android 5.0 devices.|
|Tethering||Connect the device as a mobile hotspot. Not available while running Workspace ONE Launcher on Android 5.0 devices.|
|Screen Lock||Configure screen lock settings such as a PIN or password. Not available while running Workspace ONE Launcher on Android 5.0 devices.|
|App Manager||View running applications and use the Kill app option to force stop.|
|Denied Apps||Displays a list of apps the user attempted to open from within an allowed app so admins can choose to allow those apps as needed.|
|User Information||Displays user information.|
|Help||Opens the tutorial for onboarding.|
Admin mode grants privileges that allow users to perform admin tasks from the Workspace ONE Launcher profile on the device without having to exit the launcher. You can also use Admin Mode to enable a feature, troubleshoot a problem, or exit AirWatch app.
This mode is passcode protected, which you can configure in the Preferences section of the app mode. Admin mode is only available for Multi App and Template modes.
The Preference tab from each app mode allows you to establish the Admin passcode. The Persist Admin Passcode If Kiosk Profile is Removed From Device check box prompts the user for the admin passcode if they are attempting to remove the Launcher profile from their device.
If someone tries to use the Exit Launcher setting from the device and enters the Administrative Passcode incorrectly, the option disappears after 10 unsuccessful attempts, you can restart the device and the option reappears.
There are two use cases for this option: