From registration to the last arrival.

Decide how people get a place, how they receive their ticket, and who can help when something changes.

1. Confirm the event’s home and schedule.

   Choose the organization running the event. Confirm the venue name, postal address, start and end times, and timezone. Check the public details from an attendee’s point of view, including the entrance they should use.

   See event setup

2. Decide who can attend and how many places you have.

   Choose team-issued guests, public registration, or both. Create the admission types and capacities you need, and decide whether packages or a waitlist fit the event. A contact record or waitlist place alone does not confirm admission.

3. Check payment and refund readiness before selling.

   For paid admission, complete the organizer’s Stripe Connect setup and test the checkout outcome. Publish the actual price, fees, admission conditions and event refund policy. Name the people who will review requests; an internal approval does not mean money has been returned.

   Review ticket and payment options

4. Make sure colleagues can open the right workspace.

   Have each colleague sign in, complete their required authentication and open the correct organization. Give the entrance team check-in permission and decide who can handle ticket or payment exceptions. Access across parent and child organizations must be explicitly granted.

   Review team access

5. Publish the event and open the right registration options.

   Review the dates, timezone and active ticket types before publishing. Enable the public listing and selected registration types if people will book themselves. Issue invited guests their own passes. Public registrants use verified accounts with two-step verification; their accounts do not grant workspace access.

6. Get each pass to the right guest.

   For eligible team-issued tickets, share the private claim link with the recorded recipient. Attendees can keep owned tickets in their account; printed passes, PDFs and configured wallet options offer other formats. Include the arrival time and entrance. Automatic ticket email is not included.

   See ticket preparation and delivery

7. Brief the people at the entrance.

   Test the actual device at the entrance: a compatible phone camera needs HTTPS and camera permission. A code field or text-entry scanner offers another way in. Open the correct event, check the internet connection, add a station label, and try a sample admission before the queue arrives. Check-in is online only.

Choose one person to handle exceptions so the rest of the team can keep checking tickets.

1. Check the code against the selected event.

   Scan or enter the guest’s admission code. “Admission confirmed” records the arrival. “Already checked in” means it has been used and does not add another entry. “Entry not confirmed” needs attention. A listing-verification code is not an admission code.

   Understand the check-in results

2. Look up a missing pass.

   Search the event’s ticket list by guest name or email. Check the ticket’s event and status before retrieving its code. If you only find a person record, ask the organizer to confirm whether they should receive a ticket.

3. Keep the event lead close to exceptions.

   Ask your event lead to review unknown, cancelled, already-used or payment-restricted tickets. An old pass cannot override a completed transfer or current restriction. If a request is interrupted, check its result or follow the retry option before treating it as an arrival.

4. Refresh attendance when you need the latest picture.

   Your own successful check-ins update the page. Use Refresh attendance to include activity from other stations. Check the event and station labels when you compare arrivals across the team.

A short review makes the next event easier to prepare.

1. Review the recorded arrivals.

   Refresh the event’s attendance and compare checked-in tickets with tickets still to arrive. Discuss any manual exceptions with the people who handled them so you understand what the recorded count represents.

2. Write down what your team learned.

   Record where guests needed help and how the entrance setup worked. Assign appropriate follow-up in your workspace, and keep personal notes limited to what authorized teammates need. Review open refund requests separately from attendance totals.