Access Control: Session scanning

With the session scanning (access control), you will be able to manage, control, and give access to each participant in your event. Every attendee will have their own QR Code, which improves your access control and reduces any possible fraud in your event.

This article intends to teach you how to use the session scanning feature to check attendees in and out of the event and activities.

Technical Requirements

  • Internet: Minimum of 1 Mbit per reading device.
  • Hardware: Samsung Tablets, as well as smartphones iOS 13.0 or most recent, and Android 8.0 or most recent.

How do I enable the feature?

To enable this feature, go to Settings > Tools and click on the Pass section. Then, press Edit, and toggle the button corresponding to Access control. Press End to save the changes.

Access control in Settings

If you are unable to toggle on the button, then you need to first enable the tool at the Company level.

How to use Session scanning

Registering the Checklog profile

First, you need to create a Checklog profile in the list of attendees, and with that profile, log in to the app so that it is possible to use the check-in/check-out function.

To do so, go to People > Attendees > click + Add person. Then, under Permissions select Checklog, fill out the email/username and password fields, and press Create.

Permissions Collector in attendees page

That's it! Now download the app and log in with this profile and password in the app (tablet or smartphone). Choose the login option, and enter the app using the user data and password of the checklog previously created. Search for the event and click on it to enter. Then, you will have access to the session scanning mode. 

If you are using an Android device, after logging in with the checklog profile, the user will be redirected to the session scanning screen. If you are using an iOS device, after logging in with the checklog profile, you will see the app as a normal participant. Thus, you must click on the menu and select the Session scanning option.

Setting up the Session scanning (Access control) settings

There are two options when it comes to reading the QR codes:

  1. Reading the QR codes only once: burning the credential.
  2. Reading QR Code repeatedly: no credential burning.
Reading the QR codes only once: burning the credential

By default, the QR code can only be read once at the entrance of the event/activity. For it to be read other times, the attendees would need to perform the check-out before.

This possibility is recommended when the organizer wants greater control and security in their event, not allowing the entry of the same QR code several times.

Reading QR Code repeatedly: Access control as log

With this option enabled, the same QR code can be scanned multiple times without affecting the participant's entry status. This is ideal for events where attendees' entry is not restricted based on the QR code.

To enable this option, go to Event Tools, search for the Access control as log in the Extra section and enable the feature by toggling on the corresponding switch button.

Access control as log
If you have enabled the Access control as log, but now you want to go back to the original configuration, you can disable the Access control as log tool and then log out of all read devices and log in again to reset the access control (session scanning) system. Just closing the app and opening again will not be enough, you need to log out from every cell phone/Tablet.

Reading the QR codes

Regardless of the QR code reading settings, these are the options the checklogs will be able to choose from when reading a QR code:

  1. Check-in for event: Control the entry of the entire event
  2. Check-out for event: Control the output of the entire event
Scanning the QR codes
  1. Check-in for activity: Control the input of an activity or session. Should be used at the entrance of the rooms.
  2. Check-out for activity: Control the output of an activity or session. Should be used at the exit of the rooms
Check-in/out for activity

After scanning the QR code, you will see one of these confirmation screens:

  • Green: This is a positive confirmation of input, which means that the attendee is authorized to enter the event/activity. The attendee's details will also be displayed.
Screenshot showing the successful check-in notification.
  • Red: This color represent negatives. It means that the QR Code has already been read or that the participant does not exist among attendees or is not authorized to enter that session or event.
After checking in an attendee, there is a 10 minute interval before you can check them out. There is no interval between checking out an attendee and checking them in.
Screenshot showing the unsuccessful check-in notification.
For this QR Code process, consider that there should be a read point at the exit of the event/activity, so you do not display a negative on an attendee who has authorization.

Checking in attendees through Self service (Manual)

Other than checking in attendees using their QR codes, you can also check attendees in from the Guest list. Here, you can also review the check-in status of your attendees directly from the Android and iOS versions of the mobile app.

Android app

You can check your attendees in through the Manual option by following the steps below:

  1. Tap on the three dots icon on the top right corner of the QR code reader.
  2. Tap Manual. The Presence list will be displayed, showing the name of your attendees and their check-in status.
Screenshot showing the presence list.
  1. Tap on the attendee you want to check in.

After completing the steps above, the attendee will be checked in to your event or activity.

iOS app

You can check your attendees in by clicking on their profiles following the steps below:

  1. Tap on Self service option after choosing to check in your attendees in the Event or in an Activity. The Guest list will be displayed, showing the name of your attendees and their check-in status.
Image showing the guest list of checked in and not checked in  attendees
  1. Tap on the attendee you want to check in.

After completing the steps above, the attendee will be checked in to your event or activity.

Attendees who have been added to the Check-in block list will still be visible within the attendees list. However, they cannot be successfully checked in to the event.

When scanning blocked users who do not have permission to check in, you will encounter the error message below:

Attendee not allowed

Reading Stats

You can track total numbers via the app or platform.

  • Mobile app: Click the Live stats at the event button and you will see how many attendees had their badges read (by activity and total event).
Live stats at the event

  • Live Dashboard: On the web platform, go to Analytics > Live Dashboard and you will be able to keep track of the total number of badges read (consider total check-in readings at the event) and the total number of live people, who consider only the badges read that did not check out at the event. For further information, click here.

How do I extract a detailed report?

Navigate to Analytics > Checklog reports.

Checklog reports

Click here for further information on checklog reports.

I want to perform Session scanning per day. Is this possible?

To perform Session scanning per day in your event, we recommend creating invisible activities in your calendar, such as: Day 1, Day 2, Day 3.  It is a very useful strategy to gain control of the daily information of how many participants went to the event. Every day, you can check all attendees in and out. By doing so, you will be able to know how many attendees attended each day of the event.

To have invisible activities, you will need to disable Visible for attendees in the activities details.

How many devices can one profile access simultaneously?

Refer to the list below to see the maximum number of devices you can be logged into simultaneously per account or privilege type.

  • Company administrator: 5 devices
  • Event administrator: 2 devices
  • Checklog: 1 device
  • Sponsor: 1 device


How Did We Do?