iPad Check-In — A Bigger Door Screen

Phone check-in earns its place moving through a room or down a line, scanning one code after another as people arrive. A welcome table is doing a different job: looking someone up by name instead of a code, seeing who they're arriving with, adding a walk-up who never got as far as booking online. That's the job an iPad is built for at the door — a kirtan sign-in table, a retreat check-in desk, a sound healing evening where fifty names on a clipboard become one screen everyone at the table can actually read.

At a bigger gathering, one welcome table often isn't enough — a festival with several gates, a retreat with a check-in desk in two buildings. Several iPads can run the same BrightStar event at once and stay in sync with each other. Each device checks back with the server on a short interval and folds in whatever changed elsewhere, so a guest admitted at one table shows as admitted at every other station within moments, without anyone reloading the page.

That sync is what keeps two doors from admitting the same ticket twice, but the safeguard itself doesn't live on the screen — it lives on the server. Once a ticket carries a check-in time, it isn't stamped again; the station that scans it a second time is handed back that original time instead, which is what tells the person at the table this guest already came in somewhere else. That holds even if a device drops offline for a moment, because the check is made where the record lives, not on whichever screen happens to be in front of a person.

Because a check-in device is often shared — passed between volunteers, left at a table overnight — access is controlled by device and by person, not just by whoever happens to be holding the iPad. A pairing code minted from the BrightStar dashboard is single-use and expires twelve hours after it's created, and it only opens the specific events it was minted for, so a borrowed iPad can't wander into an event it wasn't set up to see. A session can be revoked at any time, and one left alone will expire on its own.

Signing in with an account works the same way, just tied to a person instead of a device: the guest list opens for the organizer, for anyone added as a per-event collaborator with scan permission, and for a team member on the account holding that same access. Either path — a pairing code or a login — lands on the same guest list once it's open.