We’re using single-app kiosk mode, and the experience is exactly what we want except for one thing.
The app launches straight away, which is great for usability, but in some scenarios, we’d like one extra layer of control before users can access it. Think of it like a quick checkpoint before the app opens.
Is there a way to handle this without breaking the kiosk flow?
12 Views
Good question, this comes up more often than you’d expect.
In kiosk mode, access control is generally handled at the device level, not per individual app. That said, Hexnode does allow you to retain or enforce a device passcode even while the device is locked into kiosk mode.
So, while you can’t add a separate PIN just for the app itself, you can require authentication before the kiosk session becomes accessible. That way, only authorized users ever reach the app in the first place.
Exactly. Kiosk mode doesn’t automatically mean “no security.”
You can keep the device passcode enabled alongside kiosk mode, which gives you a clean and consistent security gate. Once authenticated, the user is taken directly into the single allowed app, without access to anything else on the device.
If the app itself supports an internal login or PIN, you can also layer that on top, but from an UEM perspective, the device passcode is the supported and reliable way to control access in kiosk environments.
Don't have an account? Sign up
