The browser scanner covers most doors just fine. A dedicated app exists for the ones it doesn't: a long shift running on a volunteer's own phone, a venue with spotty reception, and a door team that also needs to take money from someone who shows up without a ticket.
The BrightStar scanner app is installed on the phone rather than opened from a link, and that single difference changes how it behaves under pressure. The attendee list lives locally on the device, so a signal drop in a barn or a forest clearing doesn't turn into a stalled line of people waiting to get in. And because it's a dedicated screen rather than a browser tab, the person scanning isn't one accidental swipe away from losing their place, or competing with a text message that pops up mid-shift.
Pairing instead of logging in
Door staff do not sign in with your BrightStar account, and that's deliberate. You generate a pairing code from your dashboard, and the person working the door enters it — or scans it — once, on the phone they'll actually be using that night. From that point on, the device carries its own credential, tied to the specific events you chose and to your organization rather than to you personally.
This distinction matters more than it looks like it does. Someone standing at a door for a few hours needs the ability to admit guests. They don't need your password, they don't need to see how ticket sales are trending, and they certainly don't need a route into your payouts. Pairing draws that line at the level of the device itself: a paired phone can scan the events it was handed and nothing beyond that, so the access a volunteer holds is only ever as wide as the door they're standing at.
What a paired device can see — and what it can't
A paired device is scoped narrowly on purpose. It can see the attendee list for the events it was given, and it can see who has already checked in — the two pieces of information a door actually needs in the moment someone is standing in front of it. It cannot see your account settings, your revenue, or how sales are moving across any of your other events.
That narrowness is what makes handing a phone to a volunteer, or to someone helping out for a single night, low-stakes. If the device is lost, forgotten in a coat pocket, or just not returned at the end of the night, what was exposed is a guest list for one event — not your dashboard, not your payment details, and nothing tied to an event that phone was never paired to in the first place.
Scanning, the guest list, and selling at the door
The app is built around the actual jobs a door has to do across a shift, not just the moment of scanning a code. It reads a QR code and admits the guest. When a code won't scan — a screenshot that's too dark, a screen cracked in the wrong spot — it can look the person up by name instead, so one technical hiccup doesn't turn into a bottleneck behind them. It also shows how many people have come through so far, which is the number a door team gets asked for all night and would otherwise have to guess at.
And because people turn up at every kind of gathering without having bought a ticket in advance, the app can sell them one on the spot. That sale runs through the same payment path as every other ticket for the event, so it lands in your BrightStar reporting next to the ones sold online weeks earlier — not as a separate cash total someone has to reconcile by hand afterward.
Setting up a scanner for the door
Getting a new device ready for a shift starts from your side, before it ever reaches a volunteer's hands.
- 1Generate a pairing code from your BrightStar dashboard for the event you want that phone to cover.
- 2Have the door volunteer install the scanner app on their own phone.
- 3The volunteer enters the pairing code, or scans it, once.
- 4The device now holds its own credential, scoped to the events you chose.
- 5The phone is ready to scan tickets, look up guests by name, and sell at the door.