Power button shutdown menu appears on locked-down devices — suppress it with allowPowerOff

Android

When a user long-presses the power button on an Esper-managed Android tablet, the native Android shutdown and restart menu can still appear even on fully locked-down devices. This exposes an unintended exit path on kiosk or field-deployed hardware.

Why this happens

The Android power menu is rendered at the system level, below the layer where standard MDM restrictions apply. Suppressing it requires both an Esper Agent parameter to signal the intent and a Supervisor Plugin — signed by your device manufacturer with platform-level keys — installed as a system app. Neither component alone is sufficient.

Before you begin

Confirm you have the following before starting:

Access to the Esper Console with Blueprint edit permissions
The exact model number of your target device (brand name alone is not sufficient)
A contact at your device manufacturer (OEM) who can sign APKs with platform keys

The Supervisor Plugin is model-specific. A plugin built for one device model will not work on another, even from the same manufacturer.

Steps

Add the allowPowerOff parameter to your Blueprint. In the Esper Console, go to Blueprints and open the Blueprint assigned to your target devices, or create a new one. Navigate to Esper Settings → Advanced Android Settings and locate the Esper Agent parameters field. Enter the following JSON exactly:
```
{"dpcParams":[{"key":"allowPowerOff","value":"false"}]}
```
Save the Blueprint. This parameter instructs the Esper Agent to suppress the power menu once the Supervisor Plugin is in place.
Request the unsigned Supervisor Plugin from Esper Support. Contact Esper Support and request the unsigned Supervisor Plugin APK for your specific device model. Include the exact model number in your request. Esper will supply an unsigned APK built for that model — do not attempt to use a plugin built for a different model.
Have the APK signed by your device manufacturer. Send the unsigned APK to your OEM contact and request that they sign it using their platform keys. Platform signing grants the plugin the system-level permissions required to intercept the power button event. Retrieve the signed APK from the OEM before continuing.
Submit the signed APK back to Esper Support. Send the signed Supervisor Plugin APK to Esper Support. Esper will upload it to your tenant's backend. This step cannot be completed through the Esper Console and must be performed by Esper.
Converge the Blueprint to your devices. Once Esper confirms the plugin has been uploaded, go to Devices & Groups and select your target device. Navigate to Blueprint and click Converge. Wait for convergence to complete before testing. Convergence pushes both the updated Blueprint settings and the Supervisor Plugin to the device.

Verify: After convergence completes, long-press the power button on the device. The shutdown and restart menu should not appear. A short press should still turn off the screen normally. Check the device's Activity Feed in Devices & Groups → [Device Name] → Activity Feed to confirm the Blueprint was applied successfully.

If this doesn't resolve it

Work through these checks before contacting support:

Power menu still appears after convergence. Go to Devices & Groups → [Device Name] → Apps and confirm the Supervisor Plugin package is listed and shows as a system app. If it is absent or listed as a user app, the signing or upload step did not complete correctly.
JSON syntax error. Return to Blueprints → [Blueprint Name] → Esper Settings → Advanced Android Settings and verify the parameter JSON matches the example above exactly, including quotation marks and brackets. Re-save and re-converge if you make any corrections.
Locked or carrier-locked bootloader. Some OEMs cannot sign third-party APKs with platform keys on carrier-locked or bootloader-locked devices. If your OEM confirms this is the case, contact Esper Support to discuss model-specific alternatives.
No plugin exists for your device model yet. If Esper Support indicates the plugin has not yet been developed for your model, contact Esper Support with your device model number and expected deployment volume to request prioritization.

When contacting Esper Support, provide: the device model number, a screenshot of your Esper Agent parameter JSON from the Blueprint, confirmation of whether the Supervisor Plugin appears in the device's app list, and the Activity Feed output from the affected device.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.