Skip to main content
The Attendees page lists everyone registered for the event. Each row is a registration — one person in one event — with their name, email, ticket type, status, and when they registered. Form answers, perks, hotel stays, and activity history attach to the registration.

​
Registration statuses

​
Add an attendee from the console

Not every registration comes through the public page. Speakers, VIPs, and staff can be added from the console.
1

Choose Add attendee

Enter the person’s name and email, and pick a ticket type if the event uses them.
2

Registration is confirmed immediately

A console-added registration is confirmed on the spot. No order is involved. A registration never requires an order; the hosted checkout page creates one because that is how it registers people. The person receives the platform’s ticket email with their entry pass link, exactly as a buyer would.
If that email is already registered, the console does not create a duplicate. One person holds one registration per event.

​
Approving and rejecting

When a ticket type has requires approval switched on, public registrations land as Pending approval and wait for a decision:
  • Approve confirms the place.
  • Reject declines it. The reason recorded is internal — the applicant never sees it — and rejecting releases any redemption-code use the application consumed.
While approval is on, capacity is a soft limit: organizers decide who is admitted. The detail page shows who decided and when.

​
The attendee detail page

Choose Details on any row to open the person’s full record:
Status, ticket type, redemption code used, registration time — and the approve/reject controls when the application is pending. Edit info changes the person’s name or email.
What the person answered on the registration form, exactly as submitted. Alongside it, the submission capture: what was recorded when the form was submitted.
The person’s hosted entry pass — the page with their check-in QR code, wallet passes, certificate, and surveys. Choose Copy link to hand it over, Regenerate link if it has leaked (every earlier address stops working, including emails already sent — resend afterwards), and Resend ticket email to send the platform’s ticket email again. The card appears only while the registration is active.
Everything this person holds — perks that came with their ticket type, plus any granted directly to this one registration. Direct grants are edited here; see Perks.
Shown once the Housing module is enabled for the event: this person’s hotel stays — hotel, room type, nights and status — with a shortcut to the Stays page.
A timeline of every change to this registration — who did it, what changed, and how long after registering. Registrations from the hosted checkout, console edits, approvals, and every housing change all appear here.

​
Rules to know

  • A registration is one person in one event. It exists whether the person came through the hosted checkout or was added from the console, and it stays open until the event ends.
  • Console-added attendees need no order and are confirmed immediately.
  • Only confirmed registrations count against a ticket type’s capacity; approval mode makes that capacity soft.
  • Rejection reasons are internal only.
  • Cancelling releases the seat (and any redemption-code use) but keeps the record — the list is history as well as state.
  • Every confirmed registration receives the ticket email automatically. The entry pass opens only for the email it was sent to.