A Device Profile is a saved set of check-in settings. It decides who a device can admit, when check-in is open, how staff or guests check people in, and what message appears after a successful check-in. One profile can be used on several devices, so most events only need a few profiles.
Before You Start
Create your Registrant Types and/or Ticket offerings first. Profiles can only admit people once you get these things setup first.
Make sure mobile check-in is enabled for the Registrant Types you want to admit. To do this, go to the Event Manager App > Registration section > Forms tab > Edit the desired form > Settings tab and check the Allow Mobile Check-In setting and, if necessary, the Allow Multi-Day Check-In setting.
Add a Profile
Go to Event Manager App > Event Setup section > Admission Check-In tab and click Add Profile.
Complete the General, Check-in Modes, Admission Targets, and Display / Messages tabs, as described below.
Click Save.
General Tab
Enabled: Turns the profile on or off. New profiles start turned off, so no device can check anyone in until you enable it. You can also enable it later from the Configure a Device tab.
Name: Use a name that tells staff where or how the device is used, such as Main Entrance Tablet or Lobby Kiosk. Each profile name must be unique within the event.
Device PIN: A four-digit PIN that staff enter to open or leave the device's settings. New profiles start with 0000, so change it.
Mode: Choose Manual Check-In if event staff will check guests in, or Self Check-In if guests will check themselves in. See Admission Check-In: Overview to decide which fits.
Valid Until: The date and time after which the profile stops admitting people. If you leave it blank when creating a profile, it is set to 24 hours after the event ends.
Check-In Window: Controls when check-in is open, relative to the event's start and end.
Opens (min before start): New profiles use 120, so check-in opens two hours before the event starts.
Closes (min after end): New profiles use 0, so check-in closes when the event ends.
Result display timeouts: How long the success screen (10 seconds by default) and the error screen (20 seconds by default) stay up before the device is ready for the next person. Enter 1 to 300 seconds.
💡TIPS:
If your event starts at 12:00 PM and you want doors to open at 11:00 AM, set Opens to 60.
If you clear both Check-In Window boxes, the profile has no window. Each guest can then only be checked in on a day within their own Registrant Type or Ticket dates.
If a Registrant Type or Ticket has its own custom start and end dates, the window is measured from those dates.
Check-in Modes Tab
Choose which ways this device can check people in. At least one must be turned on.
Enable QR scanning: Uses the device camera to scan a guest's QR code.
After scan: Choose Return Home or Automatically scan another QR code. The automatic option is best for a busy line.
Scan timeout (Sec): How long the scanner waits for a code before returning to the home screen. New profiles use 30 seconds.
Enable manual code entry: Lets someone type a confirmation code or ticket number. It has its own After entry and Manual entry timeout (Sec) settings.
Enable staff search: Lets staff find a guest by name, email, phone, or code. This only appears for Manual Check-In profiles.
Default Check-in mode: The first screen opened when someone selects Launch Admission Check-In on the device. Only the methods you enabled are listed.
Admission Targets Tab
Choose which Registrant Types and Ticket offerings this device can admit.
All: The device can admit every eligible Registrant Type and Ticket offering, including any you add later.
Any: Pick specific Registrant Types and Ticket offerings from the list. At least one is required.
Allow staff to choose which admission target to use on the device: Appears when more than one target is available. Staff then pick a single Registrant Type or Ticket offering in the device's settings and the device only admits that one. This is useful when one tablet is shared between sessions or areas.
💡TIPS:
Create separate profiles for different entrances. For example, a VIP Entrance profile that only admits your VIP Ticket and a General Entrance profile that admits everyone else.
Someone scanned at a device that is not set up for their Registrant Type or Ticket sees Invalid for this device. They are not checked in.
Display / Messages Tab
Instructions: Text shown on the welcome screen of a Self Check-In device, such as "Hold your QR code up to the camera."
Failure Help: Text shown to a guest on a Self Check-In device when check-in does not work. If left blank, it says "Please see event staff."
Success Message: Shown after a successful check-in. New profiles use the default message "Check-in successful, {{FirstName}} {{LastName}}." Anything in double curly braces is replaced with that guest's information, so a guest named Alex Rivera sees "Check-in successful, Alex Rivera."
To add more guest details to the success message, save the profile, edit it again, and use the Insert a placeholder... list below the message. It inserts the placeholder where your cursor is. You can use:
For Registrants, first name, last name, confirmation code, and the short name of any field on their registration form (for example, {{TShirtSize}}).
For Ticket Holders, the ticket holder fields and ticket number (for example, {{TicketHolderFirstName}} or {{TicketNumber}}).
📝NOTES:
If a placeholder has no value for a guest, it appears blank.
The success message is limited to 300 characters and is plain text.
Success messages are only shown for a new successful check-in. A guest who is already checked in sees an Already Checked In message instead.
On a Self Check-In device, any message other than success is replaced by your Failure Help text, so guests never see detailed error information.
Manage Your Profiles
Select a profile in the list to show its action buttons.
Edit: Change the profile's settings. Changes reach devices that are already set up on their next request, with no need to reconfigure them. If you change the Enabled setting or the Mode, ClearEvent asks you to confirm first.
Show QR Code / Configure: Opens the Configure a Device tab. See Admission Check-In: Configure a Device.
Duplicate: Makes a copy named with Copy added to the end. The copy keeps the settings, PIN, and targets, but it is disabled and has its own new API key.
Delete: Removes the profile. The profile stops working on any device, but its check-in history is kept.