Livestorm · Help center

Scan tickets at the door

Updated October 8, 2026

Check people in by scanning the QR ticket their registration issued, yourself, or with whoever works the door.

What it’s for

Every registration to an in-person event issues a QR ticket: the visitor gets it on the confirmation, at a link they can keep. At the door you scan that code instead of looking anybody up, on your own device, or on the phone of whoever is standing there, through a link.

The badges you print carry their holder’s ticket, so a visitor wearing one does not need to take out their phone.

  1. Open the “Registrants” tab of an in-person page and click “Door check-in”. Every row also carries a QR button beside its check-in control.

  2. The dialog offers the three ways to work the door: scan on this device, a link for your team, or a link for anyone.

  3. “Scan tickets” opens the camera on this device. Point it at the visitor’s code, on their phone or on their badge: each scan answers with a verdict, “Checked in”, “Already checked in” (with the time they arrived), or “Not a valid ticket for this event”. The scanner stays open, so a queue moves through one code after another.

  4. Someone in the queue never registered? Switch to “On site” at the bottom of the scanner. It shows your page’s form (on an event over several days, today’s date is already ticked), and “Register and check in” adds them and marks them arrived at once. If their email is already on the list, the scanner offers to check that person in instead.

  5. Handing the door to someone else? The team link opens the same scanner for anyone signed in to this workspace. Copy it, or scan the QR beside it with the phone that will work the door.

  6. Door staff with no Livestorm account (a volunteer, the venue’s own team, an agency) need the public link, which is off until you create it. Read what it allows, create it, then share it with that team only.

  7. Someone lost their ticket? Open it from their row and copy the link. The ticket page shows no personal details, so it is safe to send as is.

    The organizer’s copy of a ticket, reopened from the registrant’s row.

Good to know

  • A scan only ever stamps an arrival, it never removes one. Undoing stays on the row’s check-in control, in the dashboard.
  • A ticket identifies a person, not a date: someone booked on several dates is admitted with the same code every day.
  • Scanning the same ticket twice keeps the first arrival time and answers “Already checked in”.
  • The public link is a key, not a password: anyone who opens it can check people in without signing in, and each scan shows them the attendee just admitted. Share it with the door team only.
  • “Replace link” issues a new one and kills the old one at once. That is the move if a link reached the wrong people. “Turn off” ends it entirely. Both are recorded in the audit log.
  • A public link never exposes your registrant list: it can admit people and read the arrival counters, nothing else. It has no “On site” tab, so it cannot add anyone.
  • A ticket link carries no name and no email. Identity only appears to whoever scans it.
  • A printed badge’s QR code is the person’s ticket, so every door reads it the same way and gives the same answers, including “Not a valid ticket for this event” for a badge from another event. See “Print attendee badges”.
  • Erasing a registrant, or anonymizing them through your retention setting, stops their ticket link from resolving, and the code on their badge with it.
  • Tickets are issued on registrations to an in-person event: an online event has no door, so no ticket.
  • Attendees can also check themselves in, at a tablet by the entrance: see “Set up a self check-in kiosk”.

Related articles

Still need help?

Ask AI for a docs-grounded answer, or talk to our team.

Sign in to ask AI Email support

Was this article helpful?