Kiosk Admin PIN not visible or kiosk URL not updating — fix via Blueprint

Android

When a device is locked in kiosk mode, you cannot change the displayed URL or retrieve the Admin PIN from the device itself — both are controlled entirely by the Blueprint applied to that device.

Why this happens

Kiosk mode on Esper-managed Android devices is enforced at the Blueprint level. The Admin PIN and the URL shown on screen are set inside the Blueprint's configuration, not stored locally on the device. Any changes must be made in the Blueprint and pushed to the device — local edits are blocked by design while kiosk mode is active.

Find the Admin PIN

1. Open the Esper Console and navigate to Blueprints → [Your Blueprint Name] → Esper Settings → Customize Settings → Admin Mode.
2. Locate the PIN field and select the eye icon to reveal the current PIN value.
3. If no custom PIN has been set, the default Admin PIN is 1234. Note the PIN before continuing — you will need it to verify changes on the device later.

Update the kiosk URL

1. In the Esper Console, navigate to Blueprints → [Your Blueprint Name] → Apps & Configuration.
2. Locate and select Google Chrome, then open Managed Configurations. Chrome Managed Configuration is the mechanism that controls which URL loads in kiosk mode — changes made here override anything previously set on the device.
3. Update the URL using the appropriate configuration key for your deployment:
   • HomepageLocation — sets the browser homepage
   • RestoreOnStartupURLs — sets the URL loaded on Chrome startup
   • OEM-specific kiosk URL keys — consult your device manufacturer's documentation if neither key above applies
4. Save the changes.
5. Select Publish Blueprint to make the updated configuration available to devices. Devices on a stable network connection will pull the change automatically, typically within 5–15 minutes.
6. To apply the change immediately without waiting, navigate to Devices & Groups → [Device Name] → Actions and select Sync Blueprint.

Verify: On the kiosk device, confirm the new URL is displayed. To enter Admin Mode and inspect device state, use the Admin PIN retrieved above. The device's Activity Feed under Devices & Groups → [Device Name] should show a successful Blueprint sync event within 5 minutes of triggering the sync.

If this doesn't resolve it

Before contacting support, check the following:

• URL still not updated after 15 minutes: Confirm the Blueprint has been published (not just saved), and that the device shows a connected status in Devices & Groups. Trigger a manual sync via Actions → Sync Blueprint and check the Activity Feed for errors.
• Managed Configuration keys not taking effect: Confirm that Google Chrome is set as the kiosk browser in the Blueprint, that you are editing the correct Blueprint applied to this device, and that you are using the correct URL policy key for your Chrome version and OEM.
• Admin PIN not working: Confirm you are reading the PIN from the Blueprint currently applied to the device — if multiple Blueprints exist, a different one may be active. Check Devices & Groups → [Device Name] → Device Details to see which Blueprint is applied.
• Unsure which tenant the device belongs to: Gather the device serial number or hardware ID and contact Esper Support.

When contacting Esper Support, include the device serial number, the Blueprint name, a screenshot of the Managed Configuration settings, and the Activity Feed log from the time of the failed sync.

Still need help?

If the Kiosk Admin PIN remains hidden or the kiosk URL still isn't updating after applying the Blueprint, submit a support ticket and include your Blueprint configuration, device name, and the specific steps you've taken to apply it.