Skip to main content

Configure and Launch Kiosk Mode

Kiosk Mode transforms an iPhone or iPad into a self service check-in and registration station for your event. Guests can scan their QR codes to check in, while walk-in attendees can register themselves directly on the device during the event using your existing Diobox Registration Forms.

This article includes the following topics:


Launch Kiosk Mode

Go to the Tools tab and select Kiosk Mode.

This opens the Kiosk Mode Launcher, where all settings can be configured before starting the kiosk. These settings are grouped into two sections:

  • QR Scanning controls how QR codes are scanned and handled during check-in, including camera selection, restrictions, and duplicate handling.

  • After Scan or Registration controls what happens after a guest scans a QR code or completes a walk-in registration, including activity tracking and automatic badge printing.


Camera Controls

Choose which camera the device should use for scanning:

  • Rear camera for standard scanning

  • Front (selfie) camera for front-facing scanning


Restricting QR Codes to Guest Segments

Kiosk Mode can limit which guests are allowed to check in on a specific device. This is useful for managing access across entrances, sessions, or restricted areas.

Settings are available under Kiosk Mode Launcher → Restrictions.

  • None: All valid QR codes can be scanned and checked in (default setting).

  • Confirmed Guests Only: Only guests with a Confirmed status can be checked in. Declined, waitlisted, or unconfirmed guests are blocked.

  • Specific Guest List: Restrict check-in to guests assigned to a selected Guest List. This can be used to control access to areas such as VIP sections or backstage.

  • Specific Form Registration: Restrict check-ins based on the form used during registration. This allows segmentation by ticket type or registration flow.


Handling Duplicates

Kiosk Mode includes controls for how duplicate QR code scans are handled.

Configure this under Kiosk Mode Launcher → Handling Duplicates.

  • Always Show Alert: Displays a “Duplicate QR Code” message when a code is scanned more than once.

  • Session-Based Alert: Allows one scan per session. Guests can check into multiple sessions, but repeated scans within the same session trigger an alert.

  • Never Show Alert: Duplicate scans do not trigger an alert. Each scan is still recorded in Guest Activity.


Event Session Tracking

Kiosk Mode can record guest activity automatically after a QR code scan or walk-in registration. This allows you to track attendance for event check-in, breakout sessions, receptions, or any other Event Activity configured in your event.

The selected activity applies to both QR code scanning and walk-in registrations:

  • When a guest scans their QR code, the selected activity is recorded immediately.

  • When a guest completes a walk-in registration, the guest is automatically created and checked in to the selected activity in a single step.

You can select which event session should be recorded from the Kiosk Mode Launcher → Activity Tracking setting.

To learn more about setting up sessions, see: Manage Event Sessions


Badge Printing

Kiosk Mode can automatically print badges after a successful guest QR code scan or walk-in registration.

This enables a fully self-service flow where guests check in and receive their badge without staff assistance.

To learn more about setup and supported printers, see: Diobox Badge Printing


Device Security

Kiosk Mode includes multiple security layers to help prevent unauthorized access to the device during self service operation. This includes both the Diobox Kiosk PIN and Apple’s Guided Access feature.

The Diobox Kiosk PIN prevents guests from exiting Kiosk Mode or accessing other areas of the Diobox app. Guided Access locks the iPhone or iPad to the Diobox app itself, preventing access to other apps, device settings, or system gestures.

For unattended kiosk setups, it is strongly recommended to enable both the Kiosk PIN and Guided Access before placing the device at the event.

Did this answer your question?