When you open the attendees view on a BrightStar event, you're looking at a live list built straight from the tickets that have actually been issued for that event. The same underlying data feeds three places at once: the attendees view in your dashboard, the guest list inside the scanner app, and the Attendance reports. Because all three read the same source rather than separate copies, a ticket scanned at the door updates what the report says without anyone having to sync or refresh anything by hand.
What counts as an attendee
The list is built one row per ticket, not one row per order, so if someone bought four tickets in a single checkout, they show up as four separate admissions rather than one line. That matters because it's the count you should trust for capacity and door planning — it reflects people who can actually walk in, not transactions. Only tickets attached to completed or free orders make the list, which is why an abandoned or still-pending checkout never inflates your numbers. Tickets that were voided, or transferred to someone else, drop off the list too, since in both cases the original holder no longer has a ticket that admits them. What's left after all of that is the working set: the people who are actually expected at your door.
Working the list on screen
The attendees view is built to be filtered and searched rather than just scrolled, which is what keeps a large guest list usable on the night:
- 1Search by name or email to find one person quickly
- 2Filter to checked in or not yet checked in
- 3Filter by ticket type to see one tier at a time
- 4Page through the list, or raise the page size to pull more rows at once
- 5Check someone in by hand when their code will not scan
What ends up in your export
The export mirrors what's on screen but carries more detail than a glance at the list gives you. It includes the attendee's name, email and phone, plus the buyer's name and email in cases where someone bought a ticket for another person. Each row also carries the ticket type and its face value, the order number and order date, and — on reserved-seating events — the section, row and seat. On the attendance side, you get whether the person checked in, the time they did, and the check-in method, which tells apart a scan made at the door from a manual check-in entered in the dashboard. If you asked custom questions at checkout, each one becomes its own column, holding that buyer's specific answer. Put together, it's the same list you work from on the night, just laid out for review afterward rather than for speed in the moment.
Exporting from anywhere in your dashboard
The export itself is a plain CSV file, which is deliberately unglamorous: it opens in any spreadsheet program and imports cleanly into almost anything else, without needing a particular tool to read it. The attendee list isn't the only place this download sits, either. The same export sits on the tickets view, on the event page, on door sales, and across the reports section — customers, discounts, transfers, upsells, tips and donations, cart recovery, and email opt-ins all have it too. The practical rule to remember is simple: wherever BrightStar is showing you a table, you can take that table with you as a file.
Who can see the list, and why the scanner shows less
An attendee list carries real contact details for real people, so it's worth treating the export the same way you'd treat any file full of personal information. Inside BrightStar, access is scoped: only you and any collaborators you've given view permission can see the full list. The scanner app, deliberately, shows less — a person's name and their ticket type, but not their email or phone — because door staff need to recognize who's arrived, not hold onto their contact information. That protection only exists inside BrightStar, though. Once a CSV has been downloaded, none of those permission controls travel with it, so it's worth being deliberate about where the file ends up and who you send it to.