VR kiosk mode is a setting that locks a headset to a single application: the device boots straight into your training app, the user cannot leave it, and the store, browser and other apps are out of reach. For anyone running VR training on shared headsets, it is the difference between a device that trains people and a device that becomes a games console the moment you look away.
Here is the part that surprises most first-time buyers: Meta Quest has no native kiosk mode. There is no toggle in the settings that says "lock to one app." To put a Quest into VR kiosk mode you install an AR/VR device-management tool — ArborXR and ManageXR are the two most common — and configure the lock from there (ArborXR, 2026). This article explains what kiosk mode does, why the extra tool is needed, and how the setup actually works.
What kiosk mode does on a training headset
Kiosk mode locks the headset to one app that launches automatically when the device powers on. The trainee puts the headset on and is already inside the scenario — no menu, no store, no way to open anything else. When they finish, you hand the headset to the next person and it behaves exactly the same way. Nothing to reset, nothing to find.
That matters because a training headset is almost never a personal device. It is shared across a shift, a classroom or a whole site. Without a lock, every hand-off is a chance for someone to close the app, open the browser, install a game or change a setting that breaks the next session. Kiosk mode removes that whole class of problem by making the training app the only thing the headset can do.
Why Meta Quest needs a device-management tool
Meta Quest has no built-in single-app lock, so the only reliable way to run VR kiosk mode is through an AR/VR device-management platform (an MDM built for headsets). The MDM installs a small companion layer on each Quest, then lets you set one app as the kiosk app and disable the ways a user could escape it (ArborXR, 2026).
The critical piece is the home button. On a plain Quest, pressing it always drops the user back into Meta Home, where the store and browser live. A headset MDM changes that behaviour — the home button either does nothing or opens a small pause menu with a "resume" option that returns to the training app, instead of exiting to the system. Without that, there is no real lock; with it, the training app is genuinely inescapable. This need for third-party management grew after Meta stopped selling its own commercial device services in February 2026 — see what the end of Meta Quest for Business means for VR training.
How to set up VR kiosk mode, step by step
The exact screens differ between ArborXR and ManageXR, but the shape of the process is the same on any headset MDM:
- 1Create an account and enrol the headset. You register the device with the platform, usually by installing a companion app on the Quest and signing in once. From then on the headset checks in with the platform over Wi-Fi.
- 2Upload or assign your training app. Push the VR training app to the device (or to a group of devices) from the platform's console rather than the public store.
- 3Set it as the kiosk app. Choose the single app the headset should lock to. This is the app that launches on power-on.
- 4Disable the escape routes. Turn off or restrict the home button, hide other apps, and lock the settings you do not want touched — Wi-Fi, boundary, volume, factory reset.
- 5Apply to a group. Save the configuration as a policy and assign it to every headset in the room at once, so a fleet is set up in one action rather than one device at a time.
Once saved, powering a headset on takes the user straight into training. There is no "how do I start the app" question for the person handing headsets out, which is often the real bottleneck in a busy session.
What to lock down (and what to leave)
A good kiosk configuration blocks everything unrelated to the session and leaves the few things staff genuinely need. Typically you lock the home button, the store, the browser and other installed apps, plus the settings menus a trainee has no reason to open. Leave yourself an admin path — a PIN or a console action — so a supervisor can still adjust Wi-Fi or the play boundary when needed.
The boundary system deserves a specific decision. Locking it prevents trainees from accidentally redrawing the safe play area mid-session, which is good; but it also means a supervisor has to unlock the device to set the boundary in a new room. Decide based on how your headsets move around. A fixed training room can lock the boundary hard; headsets that travel between sites need an easier way to reset it.
Kiosk mode and the rest of your training program
Locking the device does not touch your reporting. Kiosk mode controls what the headset can open; it does not change what the training app records. Scores, completions and time-on-task still flow to your platform exactly as before, so you lose no visibility by locking the hardware down. If anything you gain data quality, because every session is the real training app rather than someone poking around Meta Home.
That is why kiosk mode pairs naturally with a proper rollout. If you are still validating VR on a single device, our guide to running a VR training pilot with one headset covers the wider setup, and the VR course catalog shows which scenarios are ready to lock a headset to. To connect a headset and see completions land against each trainee, the help center walks through the platform side. Kiosk mode is the last mile: it makes sure the headset only ever does the job you bought it for.
