Tickets and access control
A form can issue order tickets and individual tickets, depending on its product settings. Configure the relevant products before opening registrations, then check a validated registration.
Find and resend ticketsβ
In a validated registration, the Tickets section shows QR codes, any assigned seats, and each ticketβs status. You can download a PDF ticket, all individual tickets, or the order ticket when these formats are available.
Resend tickets resends the validation email with its tickets after confirmation. Visitors also have a public page where they can retrieve their tickets. Mobile wallet support depends on the available configuration.
Distinguish an order from an admissionβ
An order ticket can help you find a registration without granting admission on its own. When each person has a ticket, scan their individual QR code for check-in.
| Status | What to do |
|---|---|
| Valid | The admission ticket can be checked in. |
| Entered | It has already been used; check the time and who checked it in. |
| Canceled | It no longer grants access to the event. |
| View only | It opens order information; find the individual ticket. |
With the required permissions, you can Mark as entered or Cancel entry from the record. Canceling an entry makes the ticket usable again; it does not refund the payment.
Prepare the reception teamβ
Open the formβs access control and prepare the volunteer access accounts for the event. Each account should be limited to the scope it needs. Check the camera and load data before visitors arrive.
Offline mode stores check-ins on the device and synchronizes them after reconnection. Two disconnected devices cannot immediately share their latest scans: assign them separate entrances and check for conflicts when the network returns. A local result must be distinguished from an admission confirmed by the server.
For validation and payment rules, see Manage submissions.