Skip to main content

Check-In App Scanning Settings Explained

The Qflow check-in app includes several scanning settings that control how barcodes are captured, how scan results are displayed, and how the app handles edge cases. All of these settings are found under the Settings tab in the check-in app.

Written by Anthony Sergeant
Updated yesterday


Aim Mode

When multiple barcodes are visible in the camera view at the same time, aim mode lets you target and select a specific barcode to scan.

With aim mode disabled (the default), the app automatically picks the first barcode it detects. This works well when guests present one barcode at a time. When multiple barcodes are visible - for example, a stack of tickets or a lanyard near another guest's badge - the app may scan the wrong one.

With aim mode enabled:

  1. Open the camera scanner.

  2. Point the camera so that the barcodes are visible on screen.

  3. A targeting box appears around each detected barcode.

  4. Tap the barcode you want to scan.

  5. The app processes only the barcode you selected.

Aim mode is useful at busy entry points where guests queue closely together, or when scanning from printed sheets with multiple barcodes per page.


Color Background

When enabled, the entire scan screen background changes colour based on the check-in result. This makes the outcome visible from a distance - ideal for busy entry points where supervisors need to monitor check-in status at a glance.

  • Green - successful check-in

  • Red - blocked guest or error

  • Amber - warning (already checked in, unfiltered guest)

Without this setting, scan results are shown as a smaller status indicator on the scan page.


Auto Reset

When enabled, the scan page automatically clears the previous scan result and resets after 5 seconds, ready for the next guest. This is the default behaviour.

If you disable auto reset, the scan result stays on screen until you manually dismiss it. This is useful if you need more time to review guest details or notes after each scan.


Allow Repeat Scans

By default, scanning a guest who has already been checked in shows an "already checked in" warning. Enabling Allow repeat scans removes this warning and processes each scan as a new check-in.

When enabled:

  • Each scan updates the guest's check-in timestamp.

  • Every scan is recorded in the guest's history.

  • No duplicate scan warnings are shown.

This setting is commonly used for session attendance tracking at conferences, where the same guest scans in at multiple breakout sessions throughout the day.


Detect Unfiltered Guests

When you apply a tag filter to the guest list (for example, filtering to only show "VIP" guests), scanning a guest who exists in the event but is not in your current filter would normally return no result.

Enabling Detect unfiltered guests changes this behaviour. If a scanned guest exists in the event but is outside your current filter, the app shows an alert with the guest's details instead of showing no result. This helps staff identify guests who may be at the wrong entrance or need to be redirected.

This setting only applies when a tag filter is active. If no filter is applied, all guests are visible and this setting has no effect.

Did this answer your question?