These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Virtual Event Platform
- Features
- Admission Workspace
Admission Workspace
Record attendee registrations within capacity and admit each attendee once when they join.
OverviewAttendees Not Yet Admitted×
Virtual Event Platform · Admission Workspace
New
Attendees Not Yet Admitted
Admissions
| Parent | Name | Line number | Attendee reference | Quantity | Reserved at | |
|---|---|---|---|---|---|---|
| EVN-54361 | Admission 100 | 530 | AR-953 | 60 | 21 Oct | |
| EVN-64055 | Admission 605 | 560 | AR-987 | 160 | 20 Oct | |
| EVN-80810 | Admission 385 | 510 | AR-201 | 630 | 17 Oct | |
| EVN-29069 | Admission 278 | 290 | AR-830 | 750 | 08 Oct | |
| EVN-65945 | Admission 330 | 410 | AR-804 | 50 | 24 Oct |
6 of 6 records
Admission 100Admissions · ADM-55227
ParentEVN-54361
Line number530
Attendee referenceAR-953
Quantity60
Reserved at21 Oct
What you can do
Know who registered and who joined
A registration records the attendee’s name, a reference such as the ticket or registration ID, the quantity of places, the price, the time it was reserved and the provider receipt for paid tickets. Each registration is a numbered line on its event. When the attendee joins, the admitted time is recorded once.
Registrations are taken only while the event is Open and the event’s capacity minus the places already reserved covers the new request. A registration with an attendee reference already on the event is refused. For a paid event, admission waits for a verified payment capture.
How the work is organized
- Capacity counted by quantity. A team registration for five uses five places against the event’s capacity.
- One admission per line. A repeated join or a second scan of the same ticket does not admit the attendee twice.
- Every attempt recorded. Each registration and admission attempt leaves an operation receipt, so a failed or repeated attempt can be explained.
What to agree during setup
Agree the attendee reference you use: your registration form’s ID, the ticketing provider’s order number or a CRM contact ID. Decide how group registrations are recorded. Agree when admission is recorded: when the attendee clicks the join link, or when the streaming platform reports them present. If registrations come from a website, plan how they reach this list.
Check the handoff on an actual case
The user conference has a capacity of 2,000. Registrations arrive from the website with each registrant’s name and registration ID. When reservations reach 1,996, a partner company registers a team of six. The registration is refused for lack of capacity, and the Event Coordinator decides with marketing whether to raise capacity through review.
On the day, the streaming platform reports each attendee as they join, and the Registration Coordinator’s list records their admitted time. One attendee’s browser reconnects three times; the same registration line is admitted once. By 10:15, 1,640 attendees have joined, and the dashboard shows admissions by hour for the support team.
What your team sees
- Attendees Not Yet Admitted — Registrations still expected, with name, reference, quantity and reserved time.
- Admitted Attendees — Registrations admitted, with price, reserved and admitted times.
- Open Events — Events currently taking registrations, with capacity and times.
Follow the work through
- Registration to admission: From an open event to registered and admitted attendees.
- Event approval to close: See how admissions feed the event close.
Plan the registration connection before importing attendees.
What it keeps track of
Data model- Admissions
- Reserved and admitted attendee lines belonging to an event.
- Events
- Virtual events moving through draft, review, approval, open and completion.
- Payment evidence
- Provider authorization, capture, refund and void evidence for event payments.
- Operation receipts
- Idempotent receipts for every guarded operation executed against an event.
Who uses it
Permissions- Registration Coordinator
- , Event Coordinator, Finance Coordinator.
- The Registration Coordinator manages registrations and admission.
- The Event Coordinator decides capacity questions.
- The Finance Coordinator verifies payments for paid events.
Set up Virtual Event Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.