Android single website kiosk setup with camera access and brightness schedulingSolved

Hello @grace_t ,

For this use case, configure the device using a Website Kiosk policy rather than a general single app kiosk with manual browser restrictions.

Recommended configuration:

1. Create an Android kiosk policy and choose Website Kiosk Settings.
2. Add the required web app URL as the kiosk website.
3. Configure the website allowlist so the kiosk browser can access only the required domain and any supporting URLs used by the web app.
4. Configure Background Apps in the kiosk policy to allow the required hardware access, such as camera access, if the web app depends on it.
5. Apply the policy to the Android Enterprise Device Owner devices.
6. Reboot a test device and confirm that the kiosk relaunches automatically without local user interaction.

In kiosk mode, access to Home and recent apps is restricted by the kiosk lockdown. If the web app needs text input, avoid using a configuration that hides or blocks the on-screen keyboard.

For brightness changes, use Hexnode Automations to schedule Peripheral Settings policy changes based on time. However, brightness behavior can be device-specific on Android. Some OEM power-saving features, adaptive brightness settings, or OS-level battery saver behavior may override MDM-pushed brightness values. This should be validated on the exact device model and OS version before deploying sealed devices.

Regards,
Simon Scott
Hexnode UEM

Website Kiosk with the allowlist got the web app locked down properly. The camera also started working after adding under background apps.

The only part I’m still not fully clear on is brightness. We want something like 85% in the daytime and 5% overnight. Is that reliable from Hexnode, or can the tablet override it?

Brightness control on Android depends on how the device firmware handles display and power management.

You can configure scheduled brightness changes using Automations, but if the device has Battery Saver, adaptive brightness, or OEM-specific display optimization enabled, those settings may reduce or override the brightness even after Hexnode UEM applies the command.

For unattended kiosk deployments, the safest approach is:

• Test scheduled brightness changes on the same device model and Android version used in production.
• Disable adaptive brightness or automatic brightness controls where the device and policy settings allow it.
• Avoid relying on Battery Saver for sealed kiosk devices if it interferes with brightness.
• Confirm the behavior after reboot, battery drain, and reconnecting to power.

If the OEM firmware enforces dimming under certain power conditions, Hexnode UEM may not be able to override that consistently. In that case, the brightness behavior should be treated as a device-specific limitation rather than a kiosk policy issue.