Using admin override configuration in kiosk mode

This guide covers how to use the admin override configuration with MANAGED INFO in kiosk or launcher mode, including key requirements and limitations for both AMAPI and custom DPC deployments.

To enable admin override in kiosk/launcher mode:

1. Configure the admin override in your MANAGED INFO deployment and set a password.
2. Provision your device in kiosk/launcher mode using either AMAPI or a custom DPC.
3. Long-press the settings icon (default or MANAGED SETTINGS) to prompt for the admin password and access the device applications list.

After entering the admin override password, a bottom sheet appears listing all available apps with launcher icons that can be opened. This includes user-installed and permitted system apps. System apps without launcher icons or those blocked by policy will not appear.

For admin override to work in AMAPI kiosk mode, only apps that are allowlisted in your AMAPI policy can be launched. Even if an app is visible, it cannot be opened unless it is included in the allowlist. To ensure the desired apps are accessible via admin override, update your AMAPI policy to include all relevant applications.

For custom DPC deployments, ensure your LockTask policy includes all apps you want to permit in kiosk mode. Only apps specified in the lockTask allowlist can be launched or switched to via admin override. Review and adjust your DPC configuration as needed to make additional apps overrideable.

AMAPI example:

"applications": [
    {
        "packageName": "com.example.app1",
        "installType": "FORCE_INSTALLED"
    },
    {
        "packageName": "com.example.app2",
        "installType": "FORCE_INSTALLED"
    }
]

Custom DPC example:

"lockTaskAllowedPackages": [
    "com.example.app1",
    "com.example.app2"
]

• Admin override only works for apps permitted by your device policy.
• Always review and update allowlists when changing which apps should be accessible via override.
• For help, contact project-support@bayton.org.