Using Native Android for shared devices supports simpler use cases that do not require as much customization as Launcher.

Prerequisites

Native Android is supported on the following:

  • Android 9.0 or later devices
  • Workspace ONE UEM Console 2102
  • Workspace ONE Intelligent Hub 2102 for Android
  • The Android EMM registration is complete using G Suite.

How It Works

To use Native Android Check-In Check-Out, during enrollment the Workspace ONE Intelligent Hub for Android creates a primary user that is set as the Device Owner, which manages the device and the lifecycle of any secondary users created later.

Once a user checks out a device, a secondary user is created silently in the background that contains all the apps and data. The secondary user can only modify or interact with the device as the secondary user. After the user checks in, or logs out, all associated data is cleared from the device and the device is ready for the user displaying the log in screen.

Applications

Consider assigning all apps to the Staging User which originally enrolled the device. This allows pre-loading of applications to the primary user so they are available when your secondary users log in without having to repush from the UEM console or having the user spend time downloading anything.

Migration from Launcher to Native Check-In Check-Out

You can migrate any existing devices meeting the above pre-requisites that are using Workspace ONE Launcher to a Native Android experience by changing the setting in the Staging section of the enrolled Staging user in the Workspace ONE UEM console.

To change the setting:

  1. Navigate to Accounts > Users > List View > Edit User for the Staging user with which the devices you would like to migrate are associated.
  2. Switch to Advanced > Staging, and under Multi User Devices choose Native under Android Shared Device Mode.
  3. Select Save.

On the device side, once the logged in user checks in (logs out of Launcher), the Workspace ONE Intelligent Hub receives the new settings from the UEM console, exits the device out of Launcher, and Intelligent Hub for Android is locked into the foreground to begin the Native Android experience for secondary users to log in.

Clear App Data Between Sessions

With the Native Android experience, all data, settings, wallpaper customizations, accounts, and other customizations are cleared when a user checks in a device.

How to End a User Session

There are several ways to end a session or switch between users when using Native Android Check-In Check-Out:

  • Users long press the power button and the End Session displays in the available options. The device switches back to the device owner and the login screen for Intelligent Hub for Android is ready for the next user.
  • When the device is locked, a native End Session option appears on the homescreen. This is useful in the event the secondary user forgets to log out and the next user does not have access to an admin passcode. Once End Session is selected, the device switches back to the device owner and the login screen for Intelligent Hub for Android is ready for the next user.
check-circle-line exclamation-circle-line close-line
Scroll to top icon