Configuring Corporate Owned Personally-Enabled Enrollment

Android Corporate Owned Personally-Enabled(COPE) mode gives Workspace ONE UEM control of the entire device while still deploying a Work profile for the user to use the device as a personal device. COPE is a hybrid between Work Profile and Work Managed Device modes.


Android 8.0+ is required to use COPE deployment on your device fleet. If you attempt to enroll a device that is not running Android 8.0, the device will automatically be enrolled as a Work Managed device.

There are several ways to enroll COPE devices:

  • Using an unique identifier or token code (Available on Android 10 or earlier versions as noted)
  • Scanning a QR code
  • Using Zero Touch enrollment
  • Using Knox Mobile Enrollment for Samsung devices. You can find information in the Knox Mobile Enrollment documentation.

Your business requirements determine which enrollment methods you want to use. You cannot enroll devices until you have completed Android EMM Registration.

Enroll with AirWatch Relay

AirWatch Relay is an application that passes information from parent devices to all child devices being enrolled into Workspace ONE UEM with Android. This process is done through and NFC bump and provisions child devices to:

  • Connect to the parent device to copy Wi-Fi network and region settings including the device date, time, and location.
  • Download the latest production version of Workspace ONE Intelligent Hub for Android.
  • Silently set the Workspace ONE Intelligent Hub as device administrator.
  • Automatically enroll into Workspace ONE UEM.

AirWatch Relay allows you to bulk enroll all child devices before deploying them to end users and eliminates end users from having to enroll their own devices. All child devices must be in factory reset mode and have NFC enabled by default to be enrolled as a COPE device.

The NFC bump process depends on the Android OS version . Since COPE is only supported on Android 8.0+ only, enrollment with AirWatch Relay will perform a single bump to connect and enroll child devices in one step.

Note Android 11 does not support AirWatch Relay NFC Bump for COPE. If attempting to enroll Android 11 devices using NFC Bump, enrollment is blocked as Google deprecated the capability.

Enroll with Workspace ONE Intelligent Hub Identifier

The Workspace ONE Intelligent Hub Identifier enrollment method is a simplified approach to enrolling COPE enabled devices. Enter a simple identifier, or hash value, on a factory reset device. After the identifier is entered, the enrollment is automated pushing down the Workspace ONE Intelligent Hub. The user only has to enter server details, user name, and password.

Note: This enrollment method is not available on Android 11 for COPE. If attempting to enroll Android 11 devices, enrollment is blocked as Google deprecated the capability.

Enroll with QR Code

QR code provisioning is an easy way to enroll a fleet of devices that do not support NFC and the NFC bump. The QR code contains a payload of key-value pairs with all the information that is needed for the device to be enrolled. Create the QR code before starting enrollment. You can generate the QR Code using the Enrollment Configuration Wizard in the Workspace ONE UEM console.

The QR code includes the Server URL and Group ID information. You can also include the user name and password or the user has to enter their credentials.

Here is the format of the text to paste into the QR Code generator:


"": false,
"": "ssid",
"": "password",
"": {
"serverurl": "",
"gid": "group_id",

Enroll with Zero Touch

Zero Touch enrollment allows for Android 8.0+ devices to be configured with Workspace ONE UEM as the enterprise mobility management provider out the box.

When the device is connected to the Internet during the device setup, the Workspace ONE Intelligent Hub is automatically downloaded and enrollment details are automatically passed to enroll the device with no user interaction.

Here are some prerequisites to consider:

Zero Touch enrollment is only supported by a limited number of mobile carriers and OEMs. Customers need to work with their carrier to ensure that zero touch provisioning is supported. Learn more about supported carriers and devices on the Google website.

check-circle-line exclamation-circle-line close-line
Scroll to top icon