Running the door
Scanner links, offline scanning, undo, and who is allowed to hand them out.
There are two ways in, and they suit different queues.
A person with a phone
Studio → your event → Door. Each staff member gets their own link. The first time they open it, it binds to their account — from then on every scan carries their name, and you can revoke that one person without touching anybody else.
It works with no signal. Scans queue on the device and sync when the connection comes back. Replaying a queue is harmless: the same ticket and the same scan can land twice without admitting anybody twice.
Offline data is local to that browser, device and hostname; it does not follow a person into another app or origin. An authorised host cutover must account for saved tickets and unsynchronised scanner queues before changing where staff open the scanner.
A screen at the counter
Studio → your event → Counter. One screen or a printed standee, and everyone arriving checks themselves in. No staff per lane, which at a busy entrance is the difference between one person and four.
Who can hand out scanner links
| Role | Can |
|---|---|
| Owner | Everything |
| Admin | Publish, invite anyone, delete the event |
| Staff | Build the event, invite crew — cannot publish or delete |
| Crew | Scan. No console screens at all |
Staff can invite crew and nothing else. That is deliberate: an organiser running your floor under contract needs to bring their own door staff without also being able to delete your event.
Undo
A mis-scan can be taken back on the device. The undo is recorded — who took it back, who had scanned it originally, when, and from which device — so you can tell a careful scanner from one who is undoing a fifth of their scans.
Counting
A two-day event scans the same ticket on both days. Everywhere a number is shown to you, that is one person, not two — attendance counts distinct tickets, not raw scans.