Scan tickets at the gate, and give volunteers a gate pass

Open the scanner

1. 1In the console, open Gate. Events show here from the day before they start until the day after they end.
2. 2Choose Scan tickets for the event. In Scanning at, keep The gate: let people in, and type the gate's name in This gate, such as North gate. Each admission records it.
3. 3Point the camera at a ticket's QR code. A USB or Bluetooth scanner that types the code works too.

Each scan answers with a colour, a sound and a vibration. A ticket is let in once a day across every phone; scan it again and the scanner says when and at which gate it came in.

Events that run over several days

An event of a day or less, a party that runs past midnight included, lets each ticket in once. An event that runs over several days, such as a three-day conference, lets each ticket in once on each of its days. After midnight the scanner starts the new day on its own, offline too.

When the network drops

Open the scanner once while online so it can download the ticket list. After that, scanning carries on without a connection. Scans wait safely on the phone and send when the network is back. If two phones let the same ticket in while offline, the scanner says A scan needs a look and shows both times, so a supervisor can find the ticket.

An offline scan the server later turns down, because the ticket had been refunded for example, is listed under Scans that didn't count for whoever runs the gate. Check that each phone shows the right date: a scan from a phone with the wrong date doesn't count.

Find someone without their QR code

Use Find someone to look them up by name, phone number or order reference, then let them in from the result. Searching by phone needs a connection: offline, search by name or order number. Someone on a guest list without a pass is shown with the reason, so you can tell them apart from a stranger.

Tables and group tickets

A ticket that lets several people in, such as a Table of 10, gives the buyer a QR code for each person. Each one is scanned on its own, so a table can arrive at different times, at different gates, and the gate counts people: Table of 10 23 of 40 in · 4 tickets.

• A scan names the pass, such as Kofi Boateng, pass 3 of 10, so "Already in" tells you which of the table came in. When the buyer names their guests, each pass shows its guest's name.
• Two phones scanning different passes of a table, offline, both let them in: they're different people.
• Two phones scanning the same pass, offline, both show it at first. When they sync, the second is flagged with A scan needs a look, as for any ticket. A table never counts more than ten people in.
• A pass the buyer passed on, or a refunded table's pass, says Not valid.

The scanner says "Each ticket lets one person in" only when every ticket for the event does. With tables, it says each QR code lets one person in.

Give a volunteer a gate pass

1. 1On the event's page, open Gate passes. The event must be published.
2. 2Enter who it's for. In Where it scans, choose a gate and name it, or one of the event's checkpoints.
3. 3Copy the link, or show its QR code, and send it to them. It's shown once.

The link opens the scanner on their phone with no account, for that event and that gate or checkpoint only. A pass for a security checkpoint can only check tickets. It stops working 6 hours after the event ends, when its checkpoint is removed, or straight away when you choose Stop pass.

A phone that's offline when you stop its pass finds out when it reconnects: it stops offering Admit and tells the volunteer to let nobody else in. Anyone it let in offline comes to Scans that didn't count, not counted yet. Choose Count as admitted for each person you accept, or close it with a note.

Roles for the door

• Gate staff scan tickets and let people in.
• Security check a ticket and who holds it, and never let anyone in.
• Box office sell tickets at the door, let buyers in, and scan.

Complimentary tickets

Choose Issue complimentary tickets, pick the ticket type and how many (up to 50), and who they're for with a phone or email. Comps count against the ticket type's quantity and are recorded in the event's activity log.