Android Kiosk Settings

Quick Setup

Create a device row first. Then use Enroll Device on that row to generate the QR. Most teams finish this in about 3 minutes.

This guide helps you create Mini MDM device rows and enroll Android kiosks and browser devices. It also covers iPhone and iPad kiosks, plus document camera defaults and device overrides. AVA uses your selected camera facing when the device exposes it. Use Guided Access for local-only iOS use cases. Use dedicated enrollment for supervised iOS kiosks. Use Device Routing to manage room access encoders and payment terminals. Kiosk mode supports Android devices, flexible browser devices, and iOS devices. Users with mini_mdm:read can view kiosk status. Users need mini_mdm:manage to create rows, enroll devices, and run kiosk actions. Changing a browser device's check-in mode also requires settings:write. The Mini MDM Device ID is the stable row ID for each kiosk record. Use it to match a physical kiosk to one specific device row. AVA saves kiosk routing rows against the Mini MDM Device ID. If you still have older device ID mappings, AVA keeps them when you save. Enrollment now starts with Create Device. Then you choose either a locked-down guest kiosk, a flexible browser device, or an iOS path.

Go to: Settings → Kiosk

---

Quick Reference

Setting	What It Controls	Staff Use It For
Kiosk access permissions	Controls view-only or management access	Decide who can run device actions
Create Device	Adds an unfulfilled logical kiosk row	Reserve a slot before enrollment
Choose device setup	Opens the locked-down, browser, or iOS chooser	Pick the right device type first
Enroll Device	Creates a one-time QR for a single kiosk row	Enroll one known device slot
Create locked-down device	Adds a managed guest check-in tablet	Lock the device into kiosk mode
Create flexible browser device	Adds a browser-paired staff device	Keep normal browser access on the device
Check-in mode	Selects CCI or ACI and regenerates the browser link	Open the intended check-in flow
iOS Guided Access	Shows the local setup tutorial for AVA Check-in	Prepare an iPhone or iPad without MDM
Dedicated Device Enrollment	Adds a supervised iPhone or iPad row	Manage iOS through Apple Business Manager
Setup	Starts ADE or kiosk setup on iOS rows	Finish iPhone/iPad provisioning
Verify and continue	Checks an installed app before lock mode	Recover a stuck app install
Setup status	Shows ADE, app, and lock progress	Track iOS provisioning
Mini MDM Device ID	Shows the stable kiosk row ID	Track one specific kiosk slot
Scope	Shows row type	Distinguish Per-device rows
Unlock Code	Shows the current unlock code	Recover a locked device
Device mode	Shows kiosk or normal-phone mode	Confirm the requested and applied Android policies
Devices list	Shows enrolled device status across all pages	Check health and last sync
Device routing	Links kiosks to room access encoders and payment terminals	Keep routing up to date
Call	Starts a video call to the kiosk device after a warning prompt	Reach a kiosk when staff need help
Auto-refreshing…	Polls device updates after QR and actions	Confirm enrollment or action results
Device actions	Restart, lock, unlock, un-enroll, or remove	Remote control and recovery
Document camera defaults	Sets the first camera for phone and tablet scans	Keep scans consistent across kiosk types
Connected devices	Counts active browser connections for a flexible browser device	Spot duplicate browser pairings
Pairing code	Connects a browser without a merchant-specific URL	Pair a browser using eight characters

---

Set Document Camera Defaults

Use Document scanner camera to set the first camera AVA opens for document scans. Choose separate defaults for Phone and Tablet and larger. Managed kiosks can inherit those defaults or override them per device.

1. Go to Settings → Kiosk.

2. In Document scanner camera, choose the Phone default.

3. Choose the Tablet and larger default.

4. Click Save camera defaults.

   ✓ AVA saves the property defaults for document scanning.

How kiosk overrides work

On a managed kiosk, Use device-class default keeps the property default. Choose Back camera or Front camera to override it for that kiosk. If the preferred camera is unavailable, AVA uses any camera it can access. On phones with both cameras, AVA follows the chosen facing at scan start.

Android reduced user agents

Some Android phones hide the Mobile token in Chrome. AVA checks the shortest screen side for those devices. Phones under 768 CSS px use Phone default. Larger screens keep Tablet and larger default.

When changes take effect

Kiosks pick up the new setting after they refresh configuration or restart the scanner. The current scan session keeps running.

Camera choice still looks wrong

What you see: A kiosk still opens the old camera after you save.

Fix:

1. Refresh the kiosk configuration.

2. Restart the scanner on that device.

3. Try the scan again.

   ✓ The kiosk should use the new default or override.

---

Kiosk Permission Access

Permission	What You Can Do	What You Cannot Do
mini_mdm:read	Open Settings → Kiosk, view device list, view statuses	Create device, enroll, show/copy unlock code, restart, lock, unlock, un-enroll, remove, save routing changes
mini_mdm:manage	Full kiosk management access	N/A

If you only have mini_mdm:read, the page stays available in view-only mode. You also see a banner explaining that management permission is required.

---

Choose Enrollment Flow

Goal	Use this action	Scope shown in table
Enroll one known kiosk slot	Create Device then choose Locked-down check-in device	Per-device
Set up a shared staff browser	Create Device then choose Flexible browser device	Flexible
Set up a supervised iPhone or iPad	Create Device then choose iOS → Dedicated Device Enrollment	Per-device
Use Guided Access on an iPhone or iPad	How to enroll → iOS → Guided Access	Local only
Remove an unused pre-created slot	Remove on an unfulfilled row	Per-device

Enrollment flow

The top card now starts device creation only. You pick the device type in the chooser before the row is created. You generate the QR from the row after the locked-down device exists.

iOS enrollment

Guided Access stays on the local device. Dedicated enrollment uses Apple Business Manager and Vouch MDM.

---

Step-by-Step: Create a Locked-Down Device

1. Go to Settings → Kiosk.
2. In the enrollment card, click Create Device.
3. In Choose device setup, click Locked-down check-in device.
4. Optional: enter a label like Front Desk 1.
5. Click Create locked-down device.

✓ You see a new row with Status: Unfulfilled. ✓ The row shows a Mini MDM Device ID. ✓ The row only shows Enroll Device and Remove.

Step-by-Step: Create a Flexible Browser Device

1. Go to Settings → Kiosk.
2. In the enrollment card, click Create Device.
3. In Choose device setup, click Flexible browser device.
4. Optional: enter a device alias like Front Desk Browser.
5. Click Create flexible browser device.
6. When the pairing dialog opens, choose Self Check-In (CCI) or Assisted Check-In (ACI).
7. Choose Connect with code, Scan QR code, or Verification link.
8. Follow the matching steps in Pair the browser.

✓ You see a new browser device row. ✓ The dialog shows the selected mode and pairing methods. ✓ The code and QR connect the browser to the selected hotel and kiosk. ✓ The verification link remains available for supported recovery flows.

Pair the Intended Browser

Each browser kiosk can have one active browser device. Use the code or QR on the browser that will operate this kiosk. To replace a browser, confirm Replace device before pairing the replacement.

Merchant context

The setup address can open without a merchant-specific URL. The pairing code resolves the configured hotel, kiosk, and check-in mode. Public pairing does not grant access to other AVA features. The setup page remains available while you complete pairing.

Pair the browser

Use the pairing method that best suits the physical browser.

Method	What you do	Best for
Connect with code	Copy and open the setup address, then enter the eight-character code	A browser that cannot scan QR codes
Scan QR code	Copy and open the setup address, then scan the displayed QR	A nearby tablet or phone camera
Verification link	Open the generated link on the intended browser	Same-browser recovery or supported legacy workflows

The setup address is the generic browser enrollment page. It appears beside the code and QR actions. Use Copy setup address on either tab, then open it on the physical kiosk browser. The setup address does not select the hotel or kiosk by itself. After you choose a pairing method, AVA keeps that method selected while the panel finishes loading.

Connect with code

1. Select Copy setup address in the pairing dialog.

2. Open the copied address on the physical browser.

3. Enter the eight-character code shown in Settings → Kiosk.

4. Submit the code.

   ✓ The browser opens the saved CCI or ACI mode for that kiosk.

The code expires after 10 minutes. Generate a new code if it expires or if you regenerate the pairing details.

Scan a QR code

1. Select Copy setup address in the pairing dialog.

2. Open the copied address on the physical browser.

3. Select Scan QR code.

4. Scan the QR shown in Settings → Kiosk.

   ✓ The browser opens the saved CCI or ACI mode for that kiosk.

The QR expires after 24 hours. Use the newest QR shown by AVA.

Use a verification link

1. Select Verification link in the pairing dialog.

2. Choose Copy link or Download QR.

3. Open the link on the intended browser, or scan its QR.

   ✓ AVA pairs the browser with the selected hotel and kiosk.

The saved kiosk mode controls the result. Changing URL text cannot switch the browser between CCI and ACI.

Pairing method changes unexpectedly

What you see: The pairing panel returns to Connect with code after you choose another method.

Fix:

1. Refresh Settings → Kiosk.

2. Open the pairing dialog again.

3. Select Scan QR code or Verification link.

4. Continue with the selected method.

   ✓ The selected method stays open while its pairing details load.

Keep Browser Ownership Consistent

AVA links each flexible browser device to one browser installation. This prevents another computer from operating the same kiosk accidentally.

Situation	Result	What you should do
First pairing	The browser becomes the kiosk owner.	Keep using that browser.
Re-verification on the same browser	The kiosk remains connected.	Generate a new link and open it there.
Fresh pairing opened on another browser	AVA asks for explicit replacement confirmation.	Confirm Replace device only for the intended replacement.
Used code or QR submitted again	AVA rejects the consumed pairing attempt.	Generate a new code or QR from Settings → Kiosk.
Replacing the physical browser	The trusted replacement challenge authorizes the replacement.	Confirm replacement, then pair the new browser.

If AVA finds legacy duplicate bindings, the newest successful pairing becomes authoritative. Older duplicate bindings are cleared and no longer resolve to the kiosk.

Each flexible browser device shows Connected devices in its device row. The count includes active, verified browser connections for the same browser installation. A count above one means that browser is paired with multiple browser device rows.

When duplicate connections exist, AVA highlights the count in red. The page also shows an Affected browser devices warning with each alias, browser, and last-seen time. Chromium Edge appears as Edge, including its correct browser version.

Duplicate browser connection

Do not keep using duplicate rows for the same physical browser. Create a new flexible browser device and open its new verification link on the intended browser. This removes the extra bindings and gives the browser one clear kiosk owner.

Safe re-verification

You can re-verify an already paired browser with a fresh link. You can replay that link on the same browser while it remains valid. The replay keeps the kiosk connected and does not rotate access data. Use Replace device to replace the browser binding on another device. The ACI guest-worker pairing remains connected during that replacement.

Recover a paired browser after storage loss

AVA stores the browser installation identity in durable browser storage. It also keeps a backup identity for recovery when the local copy disappears.

If you clear site data or local browser storage, reopen the kiosk in the same browser installation. AVA can recover the existing identity before pairing or staff verification. This keeps the kiosk binding and ACI authorization when recovery succeeds.

1. Reopen the kiosk on the same device and browser.

2. Keep the pairing or ACI page open while AVA checks the saved identity.

3. Wait for the kiosk status or ACI readiness status to return.

4. Select Refresh if the status remains unchanged.

5. Use Verify Device or a same-browser verification link if AVA requests verification.

   ✓ The original browser binding remains connected when its durable identity is available.

Private browsing and new browser profiles

Private windows and new browser profiles have separate, temporary storage. They cannot recover the identity from your normal kiosk browser. Use the original browser profile for daily kiosk operation. Pair and verify a private or new profile again before using it.

Multiple tabs

Open kiosk setup in only one new tab at a time. AVA prevents conflicting first-time identities from replacing the saved browser identity.

Browser pairing does not complete

What you see: The browser rejects the code, QR, or verification link.

Fix:

1. Confirm the code has fewer than 10 minutes of age.

2. Use the newest code or QR from the pairing dialog.

3. Confirm you opened the setup address on the intended browser.

4. If replacing a browser, confirm Replace device first.

5. Retry from Settings → Kiosk.

   ✓ AVA should show the selected kiosk as connected.

Do not reuse a consumed code or QR. Only a same-browser verification-link replay can recover an existing binding.

If localStorage was cleared, keep the same browser open and wait for identity recovery. Use a fresh verification link only when AVA asks for it.

Pairing stopped after a network failure

What you see: The browser shows a connection error after submitting pairing details.

Fix:

1. Restore the browser's internet connection.

2. Keep the pairing page open.

3. Select Retry when AVA offers it.

4. Check the read-only kiosk status in Settings → Kiosk.

5. Generate new pairing details only if the kiosk remains unpaired.

   ✓ A completed pairing remains connected after a lost response.

Change a Browser Device's Check-In Mode

Use the pairing dialog when a browser must switch between guest-led and staff-led check-in. Changing the mode saves the kiosk mode and creates new pairing details.

1. Go to Settings → Kiosk.

2. Find the flexible browser device.

3. Click Get verify link.

4. In the Check-in mode section, choose Self Check-In (CCI) or Assisted Check-In (ACI).

5. Choose Connect with code, Scan QR code, or Verification link.

   ✓ The old pairing details disappear while the replacement is pending. ✓ The new code, QR, or link matches the saved check-in mode. ✓ The previous pairing details are cancelled.

Mode change permission

You need both mini_mdm:manage and settings:write to change the browser check-in mode. Without settings:write, the mode choices are disabled.

Open Copy link, Show QR, or Download QR after the new pairing details appear. Share replacement pairing details only with the target browser device.

After you select Copy link, the button shows a check mark and Copied! for two seconds. Each kiosk row shows its own copied state. If copying fails, AVA shows an error notification.

For ACI staff verification, display Show QR on another screen. On the intended ACI browser, staff select Verify Device and scan this QR. The in-page scanner keeps the browser's Web Clip, PWA, or wrapper context active.

Permission-aware controls

Users with mini_mdm:read can view kiosk status. Creating devices and managing kiosk rows require mini_mdm:manage. Enrollment actions require mini_mdm:enroll. Changing a browser device's check-in mode requires settings:write. AVA explains the missing permission when it disables a control or rejects an action.

Step-by-Step: Create a Supervised iPhone or iPad

Register First

Contact Vouch support before you create the device row. The iPhone or iPad must be registered in Apple Business Manager first.

1. Go to Settings → Kiosk.
2. In the enrollment card, click Create Device.
3. In Choose device setup, click iOS.
4. Click Dedicated Device Enrollment.
5. Enter an optional label and the iPhone or iPad serial number.
6. Click Create and assign.

✓ Streamliner creates the logical device row. ✓ The iOS setup modal opens and starts ADE setup. ✓ You see ADE Connected, ADE Synced, ADE Profile Assigned, and Ready to Erase iPhone/iPad.

Step-by-Step: Use Guided Access

Local only

Guided Access keeps the device local. Streamliner cannot remotely install, lock, unlock, restart, or erase it.

1. Go to Settings → Kiosk.
2. Click How to enroll.
3. Click iOS.
4. Click Guided Access.
5. Follow the tutorial cards for Home Screen, Guided Access, and AVA Check-in.

✓ You can use AVA Check-in in a local single-app setup. ✓ The device stays outside supervised MDM management.

Step-by-Step: Finish iOS Setup on an Enrolled Device

1. Find the iOS device row.
2. Click Setup.
3. Click Start kiosk setup or Start setup ADE.
4. Wait for the status cards to progress.
5. If the app install stalls, click Verify and continue.

✓ The modal shows license, install, and lock mode progress. ✓ The row reaches Ready when kiosk setup finishes.

---

Step-by-Step: Enroll a Device

Factory Reset Required

Enrollment requires a factory-reset device. All data on the device will be erased.

1. Factory reset the device.
2. Turn on the device and tap the screen 6 times to open the QR scanner.
3. On the matching row, click Enroll Device.
4. Scan the QR in the Enroll Device QR Code modal.
5. Complete the device setup steps.
6. Return to Settings → Kiosk and click Refresh.

✓ The row changes to Status: Enrolled. ✓ The row now shows Restart, Lock, Unlock, and Un-enroll. ✓ The QR is one-time use and lasts 3 hours.

---

Step-by-Step: View the Unlock Code

1. Find the Unlock Code card.
2. Click Show to reveal the code.
3. Click Copy code to save it.

✓ You see “Unlock code copied”.

---

Switch an Android Device Between Modes

Switch an enrolled Android device between locked kiosk mode and normal-phone mode. The device stays enrolled during this change.

Keep the Kiosk PIN Ready

You need the kiosk PIN to approve a mode change. Do not share the PIN with guests.

1. Go to Settings → Kiosk.

2. Find the enrolled Android device.

3. Open the device mode control.

4. Choose Kiosk mode or Normal-phone mode.

5. Enter the kiosk PIN when prompted.

6. Confirm the change.

7. Click Refresh and check the device mode status.

   ✓ AVA records the requested mode and sends the matching Android policy. ✓ The device remains Android Enterprise enrolled. ✓ Switching modes does not un-enroll or factory reset the device.

Policy status

The requested mode and Android-applied mode can differ briefly while the device is offline. Wait for the device to reconnect, then refresh Settings → Kiosk.

Understand policy status

Click the device row or its expand control to show policy status details.

Status	Meaning	What you should do
Requested	AVA sent the selected mode to Android.	Wait while the device receives the policy.
Pending	Android has not confirmed the policy yet.	Keep the device online, then click Refresh status.
Applied	Android confirmed the requested mode.	Continue using the device.
Retry needed	Android has not confirmed the change.	Click Refresh status, or Restart device, then refresh again.

The status panel checks pending changes automatically for a short period. After that period, use Refresh status when the device is online.

Requested versus applied

The device can show the requested policy before Android applies it. Treat Applied as confirmation that the device changed mode.

Mode change is rejected

What you see: AVA rejects the mode change or says the kiosk PIN is invalid.

Fix:

1. Confirm you selected the correct enrolled Android device.
2. Enter the current kiosk PIN from the Unlock Code card.
3. Do not reuse an old PIN after an administrator changes it.
4. Retry the mode change.
5. Contact support if the current PIN still fails.

Device stays in the previous mode

What you see: The requested mode changes, but the Android device stays locked or flexible.

Fix:

1. Confirm the device is online and charged.
2. Leave the device connected to the internet.
3. Wait for the device to receive its updated policy.
4. Click Refresh in the Devices section.
5. Compare the requested mode with the Android-applied mode.
6. Contact support if they still differ after the device reconnects.

Step-by-Step: Manage Devices

Refresh the List

1. Click Refresh in the Devices header.

✓ You see “Refreshed (synced X, removed Y)”. ✓ If your property has many devices, the list loads all pages automatically.

Confirm a legacy kiosk is still enrolled

AVA recognizes active kiosks created by older enrollment flows. Their rows remain available after you refresh the device list.

1. Click Refresh in the Devices header.

2. Find the kiosk by its Mini MDM Device ID or physical device ID.

3. Confirm its status remains Enrolled.

   ✓ Active legacy kiosks remain available for supported device actions.

Do not remove or re-enroll the row only because it lacks newer enrollment metadata.

Restart, Lock, or Unlock

1. Find the device row.
2. Click Restart, Lock, or Unlock.

✓ You see “Action completed”. ✓ The page enters Auto-refreshing… briefly to confirm the new device state.

After you click Lock or Unlock, both actions remain available. Only the action currently being sent is disabled. This lets you recover from a newer mode request without waiting for the first request to finish.

If a mode request remains pending, expand its policy status row. Click Refresh status first, then click Restart device if the status stays unchanged.

Start a call to a kiosk device

Before You Confirm

The call modal now shows an amber warning box. It warns you that the call may interrupt guest activity on that kiosk.

1. Find an enrolled device row.

2. Click Call.

3. Confirm the warning in the modal.

4. Click Start call.

   ✓ Streamliner starts a video call to that kiosk device. ✓ Use this when you need to reach the kiosk from the back office. ✓ The warning reminds you that it may interrupt ongoing guest activity.

Un-enroll a Device

Un-enroll Resets the Device

Un-enrolling can factory reset the device.

1. Click Un-enroll.
2. Confirm the warning.

✓ The device disappears from the list after refresh.

Remove a stale managed kiosk setup

Use Remove this device when a managed kiosk setup remains after Mini MDM no longer shows the device enrolled. This removes the old Check-in Connect setup and disconnects its Guest Tablet pairing.

Before removal, clear any encoder routing for that kiosk. AVA checks the latest Mini MDM status and visible Room Access mappings immediately before removal.

1. Open Settings → Kiosk.
2. Refresh the managed-device list.
3. Confirm the device is no longer enrolled.
4. Open the device's Settings.
5. Confirm the device is no longer serving guests.
6. Open Device Routing.
7. Clear the kiosk's encoder mapping, then click Save mappings.
8. Return to the device settings and click Remove this device.
9. Review the warning, then click Remove.

✓ The old kiosk setup disappears after the removal refreshes. ✓ The Guest Tablet pairing is disconnected.

Removal checks routing first

AVA blocks removal when it finds encoder routing for the kiosk. It also blocks removal when Room Access routing cannot be verified.

Legacy kiosk rows do not show Remove this device. Clear their encoder routing from Device Routing, then save the row. Browser-device removal continues through the existing browser removal flow.

Device Routing

Use the Device Routing card to connect each enrolled kiosk to the right room access encoder and payment terminals. Kiosk routing now lives here, not on the Room Access page. Legacy-only rows still appear when a kiosk has no MDM, flexible browser, or kiosk-device-model record. AVA keeps existing aliases, notes, encoder links, and terminal links when it updates older rows.

1. Scroll to Device Routing.
2. Make sure at least one kiosk device is enrolled.
3. Expand a device row.
4. Choose the linked Room Access Encoder and Payment Terminals.
5. Click Save mappings.

✓ The device row shows the linked encoder and terminal count. ✓ If no devices are enrolled yet, the card shows an empty state instead of routing rows. ✓ Read-only users can view routing data but cannot edit or save it.

What you see when old device IDs still appear

What you see: A row still uses the older Android device ID, or shows a Legacy kiosk pill, after you save.

Fix:

1. Click Refresh.
2. Open the same device row again.
3. Click Save mappings once more.
4. Confirm the row now shows the Mini MDM Device ID.
5. If it still shows a legacy row, keep using the same kiosk record.

---

Troubleshooting

QR code does not generate

What you see: A red error message after clicking Enroll Device.

Fix:

1. Refresh the page.
2. Open Enroll Device on the same row again.
3. If it still fails, contact support.

Devices list stays empty

What you see: “No devices enrolled yet.” after enrollment.

Fix:

1. Click Refresh.
2. Keep the page open for at least one auto-refresh cycle.
3. Confirm the device finished setup.
4. If still empty, refresh once more.

An active legacy kiosk looks unfulfilled

What you see: A kiosk created before the current enrollment flow shows the wrong enrollment status.

Fix:

1. Click Refresh in the Devices section.

2. Match the row using its Mini MDM Device ID or physical device ID.

3. Confirm the kiosk is online and can receive device actions.

4. Do not remove or re-enroll the row while it remains active.

5. Contact support if the status remains incorrect after refresh.

   ✓ AVA should preserve the active kiosk row and its available actions.

Remove this device is unavailable

What you see: You cannot remove a managed kiosk setup.

Fix:

1. Refresh the managed-device list.

2. Confirm Mini MDM no longer shows the device as Enrolled.

3. Open Device Routing and clear the kiosk's encoder mapping.

4. Click Save mappings.

5. Open the device settings again.

   ✓ Remove this device appears only after AVA confirms the setup is stale.

If routing cannot be checked, AVA keeps the setup. Contact support with the kiosk name and the displayed error.

Removal is blocked by encoder routing

What you see: Removal reports that encoder routing must be removed first.

Fix:

1. Open Settings → Kiosk → Device Routing.

2. Expand the affected kiosk.

3. Clear its Room Access Encoder selection.

4. Click Save mappings.

5. Open the device settings and retry Remove this device.

   ✓ AVA removes the stale setup after the routing no longer matches the kiosk.

Device routing shows no devices yet

What you see: The Device Routing card shows “No enrolled devices yet.”

Fix:

1. Enroll at least one kiosk device first.
2. Click Refresh in the Devices section.
3. Return to Device Routing and expand the new device row.

Actions fail

What you see: “Action failed” after Restart, Lock, or Unlock.

Fix:

1. Confirm the device is online.
2. Try the action again.
3. Refresh the list and check the status.

Call is unavailable

What you see: The Call button is missing or disabled.

Fix:

1. Confirm the row is enrolled.
2. Confirm you have mini_mdm:manage.
3. Refresh the page and try again.

Row shows only Enroll Device and Remove

What you see: You only see Enroll Device and Remove on a row.

Fix:

1. Check Status on that row.
2. If status is Unfulfilled, this is expected.
3. Click Enroll Device and complete setup.
4. Click Refresh and confirm status becomes Enrolled.

Kiosk buttons are disabled

What you see: Create Device, Show, Copy code, or device action buttons are disabled.

Fix:

1. Confirm your role includes mini_mdm:manage.
2. If you only have mini_mdm:read, ask an admin to update your role permissions.
3. Refresh the page after permission changes.

Kiosk access or entitlement is unavailable

What you see: AVA shows that kiosk management is unavailable, or an action returns an entitlement error.

Fix:

1. Confirm you selected the correct hotel context.

2. Confirm your role includes mini_mdm:read to view kiosk devices.

3. Confirm your role includes mini_mdm:manage for device management.

4. Confirm your role includes mini_mdm:enroll for enrollment actions.

5. Confirm your role includes settings:write to change browser check-in mode.

6. Ask your administrator to confirm the hotel's plan includes the kiosk feature.

7. Refresh Settings → Kiosk and retry the action.

   ✓ The page shows the controls allowed by your current access.

Auto-refreshing does not clear

What you see: Auto-refreshing… or Refresh stays disabled longer than expected.

The latest completed refresh clears the loading state, even when manual refresh overlaps automatic polling.

Fix:

1. Wait 45 seconds to allow the polling window to finish.
2. Click Refresh once when the control becomes available.
3. If it remains disabled, reload Settings → Kiosk.
4. If it repeats, check network stability on the kiosk device.

Unfulfilled row never enrolls

What you see: The row stays Unfulfilled after you scan the QR.

Fix:

1. Click Refresh.
2. Open Enroll Device again on the same row.
3. Confirm you used the right device row.
4. If it still fails, contact support.

Verification link does not open the selected flow

What you see: The browser device opens the wrong flow or shows a pairing error.

Fix:

1. Open the browser pairing dialog.
2. Choose Self Check-In (CCI) or Assisted Check-In (ACI).
3. Choose Verification link.
4. Select Copy link or Download QR.
5. Open the new link on the physical browser device.
6. If the link still opens the wrong flow, contact support.

Mode change closes the verification modal

What you see: The mode saves, but the dialog closes before new pairing details appear.

Fix:

1. Return to Settings → Kiosk.

2. Click Get verify link for the same browser device.

3. Confirm the selected mode.

4. Choose Connect with code, Scan QR code, or Verification link.

5. Pair the target browser with the new code, QR, or link.

   ✓ The replacement pairing details use the saved mode.

Verification link was already used

What you see: The browser device rejects a code, QR, or verification link.

Fix:

1. Generate new pairing details from Settings → Kiosk.
2. Open the setup address on the target browser.
3. Enter the new code, scan the new QR, or open the new link.
4. Do not reuse a consumed code or QR.
5. If the new pairing details still fail, contact support.

The kiosk is connected to a different device

What you see: "This kiosk is already connected to a different device."

Fix:

1. Return to Settings → Kiosk.

2. Open the pairing dialog for the kiosk.

3. Select Replace device and confirm the replacement.

4. Open the setup address on the browser that should operate the kiosk.

5. Enter the new code, scan the new QR, or open the new link.

6. Refresh the kiosk page after pairing.

   ✓ AVA replaces the old browser binding with the newly authorized browser.

Replacement requires confirmation

An ordinary code, QR, or link cannot take over an existing kiosk binding. Confirm Replace device before pairing a replacement browser.

The browser is connected to multiple kiosks

What you see: The Connected devices count is above one, or you see the Affected browser devices warning.

Fix:

1. In Settings → Kiosk, create a new Flexible browser device row.

2. Choose the required check-in mode.

3. Generate new pairing details.

4. Open the setup address on the intended browser.

5. Pair the browser, then click Refresh.

6. Confirm the duplicate warning is gone.

   ✓ The new browser row has one clear kiosk owner.

Browser details in the warning

The warning lists the affected aliases, detected browsers, and last-seen times. Use these details to identify the browser that should remain in service.

The kiosk needs a new browser device

What you see: "This kiosk needs a new browser device in Streamliner before it can be connected again."

Fix:

1. Return to Settings → Kiosk.

2. Open the pairing dialog for the existing browser device.

3. Choose Self Check-In (CCI) or Assisted Check-In (ACI).

4. Select Replace device and confirm the replacement.

5. Open the setup address on the replacement browser.

6. Enter the new code, scan the new QR, or open the new link.

   ✓ The replacement browser receives the kiosk binding.

If the replacement pairing still fails, create a new Flexible browser device row.

iOS setup failed

What you see: The iOS setup modal shows Setup failed or an Apple license error.

Fix:

1. Confirm Apple Business Manager is connected.
2. Confirm the Vouch MDM assignment is active.
3. Check that Apple Apps and Books has free licenses.
4. Click Retry setup after you fix the issue.

App stays installing

What you see: The iOS modal stays on Installing app.

Fix:

1. Check the iPhone or iPad directly.
2. Confirm ava.kiosk is already installed or can install.
3. Click Verify and continue.
4. Wait for Starting lock mode.

Setup button is missing

What you see: The iOS row shows Setup required and no Setup button.

Fix:

1. Click Refresh and wait for Apple enrollment to finish.
2. Confirm the serial number is correct.
3. Confirm the device is registered in Apple Business Manager.
4. Remove the row if you added the wrong device.

---

Still Stuck?

Contact success@vouch-technologies.com if:

• ❌ QR generation fails after several tries
• ❌ Devices never appear after enrollment
• ❌ Actions fail for more than 10 minutes

Helpful to include:

• Device model and serial number
• Screenshot of the error message
• Time the issue started

Related Guides

• Video Call Settings
• Room Access Overview
• On-Property IP Whitelist