Before You Begin
Confirm the following before configuring anything in Google Admin Console:- ChromeOS devices: Kiosk mode is native to ChromeOS.
- Managed licenses: Devices must be enrolled in your school’s Google Workspace domain.
- Dedicated Organizational Unit (OU): Create a specific OU (for example, “Hall Pass Kiosks”) for these devices. This keeps the restrictive kiosk settings from applying to students’ personal logins.
Install Hall Pass as a PWA in Kiosk Mode
Instead of installing through a user’s browser, you’ll force-install the app at the device level.- Log in to the Google Admin Console.
- Go to Devices > Chrome > Apps & extensions > Kiosks.
- Select the OU you created on the left side.
- Select the yellow (+) button in the bottom right, then select Add by URL.
- Enter the Hall Pass application URL.
- Under Installation Policy, set it to Installed.
Configure Auto-Launch
Auto-launch ensures the device boots directly into Hall Pass without showing a login screen.- In the Kiosks menu, find the Auto-launch app dropdown at the top of the list.
- Select your Hall Pass app from the list.
- Select Save in the top right.
Lock Down Device Settings
Configure the following settings in Devices > Chrome > Settings > Device Settings to prevent students from exiting the kiosk:Prevent Back-Navigation
Since kiosk mode has no browser back button, configure these additional settings to prevent navigation out of Hall Pass:- In GAC, go to User & Browser Settings.
- Search for Overscroll history navigation.
- Set it to Disabled.
- Verify the result: Students can no longer swipe to navigate back out of the app.
For standard Hall Pass kiosk deployment, the PWA method described in this article is the recommended approach. It supports Auto-launch and receives remote updates automatically. Isolated Web Apps (IWAs) are restricted to specific enterprise partners for high-security hardware access and aren’t suitable for standard Hall Pass deployments.