In modern Enterprise Mobility Management (EMM), the COPE model (Corporate-Owned, Personally Enabled) has become a preferred option for organizations that want full ownership of the device while still allowing personal use. This mixed-use scenario provides flexibility for employees but also introduces technical limitations that directly affect the way managed properties and App-level permissions behave on Android COPE devices.
Because COPE Enrollment separates the Device into two distinct spaces—a fully managed Work Profile and a Personal Profile outside corporate control—certain Policies, restrictions, and permission grants simply cannot be applied at the Device level. This differs significantly from fully managed, dedicated, or work-managed deployments, where the enterprise has broader administrative control.
Key limitations
Permissions apply only to the Work Profile
Any permission granted, denied, or required through managed properties affects Apps inside the work profile only. Administrators cannot enforce permissions on Apps in the Personal Profile.
Sensitive permissions cannot be pre-granted by IT
Even within the Work Profile, permissions such as camera, location, or microphone cannot always be auto-granted. The user must manually approve them.
Factory reset cannot be blocked
Users retain the ability to reset the entire device to factory settings. In COPE mode, EMM solutions—including Applivery—cannot disable or restrict this option.
Location control is limited
Administrators can request or restrict location access only within the work profile. They cannot force Device-wide location tracking or enforce continuous location access.
Phone and SMS permissions are not manageable
Calls and SMS belong to the Personal Profile by design; therefore, related permissions cannot be restricted, granted, or controlled from the Work Profile.
Global Device-level restrictions cannot be enforced
Policies related to screen lock requirements, disabling the camera, controlling Bluetooth, or modifying system network settings apply only to the Work Profile and do not affect personal usage.
Sensitive Personal-Profile permissions cannot be controlled
Access to contacts, call logs, SMS, shared storage, and other privacy-sensitive Resources cannot be automatically granted or denied by the EMM—either in the Personal Profile or, in some cases, even within the Work Profile.
Summary table
Permission | Can it be pre-granted or blocked? |
|---|---|
| ❌ |
| ❌ |
| ❌ |
| ❌ |
| ❌ |
| ❌ |
| ❌ |
| ❌ |
| ❌ |
Block Factory Reset | ❌ |
These limitations arise from Android’s privacy-by-design approach for COPE Enrollment. The OS intentionally ensures that personal data, activity, and system-level capabilities remain under user control, preventing administrators from silently configuring or restricting certain behaviors—even on company-owned hardware.
On COPE Devices managed through Applivery, Policies and permissions apply fully and exclusively to the Work Profile, while the Personal Profile remains protected from administrative control. This also means that certain actions—such as blocking factory resets, enforcing Device-wide restrictions, or automatically granting sensitive permissions through managed properties—are not technically possible.
Understanding these constraints is essential when designing corporate Policies, ensuring that management strategies are aligned with COPE’s actual capabilities and Android’s built-in privacy protections.