The Device Policy Management framework provides APIs to create security-aware applications that are useful in enterprise settings.

Overview

The primary purpose of the DPM(Device Policy Management) framework is to support enterprise applications, which require integration with policies enforced on the device to restrict their operations on some circumstance, such as Exchange ActiveSync or corporate apps.
The device policy API supports the policies listed in the below table, and any application can subscribe those policies by registering policy changed callback to the device policy manager.

Policy List

Policy Name	State	Description
wifi	allowed / disallowed	Specifies wether the use of Wi-Fi is allowed or not
wifi-hotspot	allowed / disallowed	Specifies whether the use of Wi-Fi hotspot is allowed or not
bluetooth	allowed / disallowed	Specifies whether the use of bluetooth is allowed or not
camera	allowed / disallowed	Specifies whether the use of camera is allowed or not
microphone	allowed / disallowed	Specifies whether the use of microphone is allowed or not
location	allowed / disallowed	Specifies whether the use of GPS is allowed or not
external-storage	allowed / disallowed	Specifies whether the use of external storage is allowed or not
text-messaging	allowed / disallowed	Specifies whether the use of text messaging is allowed or not
pop-imap-email	allowed / disallowed	Specifies whether the use of POP/IMAP Email is allowed or not
browser	allowed / disallowed	Specifies whether the use of browser is allowed or not
bluetooth-tethering	allowed / disallowed	Specifies whether the use of bluetooth tethering is allowed or not
usb-tethering	allowed / disallowed	Specifies whether the use of usb tethering is allowed or not

Signal List

Signal Name	Object	Description
on-admin-client-registered	Policy admin client name	Triggered by the device policy manager when new policy admin client is registered
on-admin-client-deregistered	Policy admin client name	Triggered by the device policy manager when policy admin client is deregistered

Privilege

In order to enforce policy on the device, the client must be registered to the device policy manager as the device admin client by enrollment process. Other unregistered application are only allowed to subscribe policy change notification published by the device policy manager.