Event registration access and lifecycle
Reference how event discovery, sign-in, registration details, approval states, cancellation, and attendee-only information work.
Event discovery can be public, but every registration belongs to a signed-in Infra One user and follows a host-controlled lifecycle.
Discovery and authentication
- Published events appear at
https://events.infra.one/{organization-slug}. - Published and hidden events are available by direct link at
https://events.infra.one/{organization-slug}/{event-slug}. - Hidden events are unlisted, not private; someone who has the direct link can open them.
- Draft events return not found unless the viewer can manage them.
- Selecting Register while signed out goes to sign-in, returns to the exact event, and creates the attendance if that user does not already have one.
Registration creation
A new self-service attendance starts as Pending. The event may then require answers under Please tell us about yourself, including organizer-defined questions and companion details. Organizer preregistration instead creates a new Accepted attendance directly.
Creating the attendance and saving the additional answers are separate operations. The attendance can already exist while the details panel is still asking for required answers. The panel remains until its required visible answers are complete.
State transitions
| From | Action | To |
|---|---|---|
| No attendance | Select Register or return from its sign-in flow | Pending |
| No attendance | Organizer selects Register attendees for a user without an existing registration | Accepted |
| Pending | Organizer selects Accept or Reject | Accepted or Rejected |
| Pending | Organizer assigns an evaluator | Under evaluation |
| Under evaluation | Evaluator or authorized manager decides | Accepted or Rejected |
| Pending or Accepted | Attendee selects cancelling your registration before the event ends | Cancelled |
| Cancelled | Attendee selects Register before the event ends | Pending |
| Accepted, Rejected, or Under evaluation | Organizer selects Status reset | Pending |
| Any state except Cancelled | Organizer selects Mark as cancelled | Cancelled |
Register attendees creates a new Accepted registration directly; it does not upgrade an existing registration or pass it through Pending.
While a row remains Rejected, the attendee has no reapply control. Status reset returns it to Pending immediately. Mark as cancelled makes Register available; before the event ends, the attendee must select Register to return the same row to Pending.
An Under evaluation attendee cannot cancel their own registration. A manager can clear or reset the evaluator to return the row to Pending, or use Mark as cancelled to move it to Cancelled.
Attendee-facing states
- Pending and Under evaluation both show Waiting for confirmation from the host.
- Accepted shows You're in!
- Rejected shows Thank you for your interest!
- Cancelled restores Register.
Pending and Accepted attendees can cancel before an exact-date event ends. The confirmation warns: Cancel your registration? If you change your mind, you must reapply.
Attendee-only information
Acceptance can control access to:
- the exact venue when Show location to is confirmed attendees;
- the agenda when Show agenda page is confirmed attendees;
- the full attendee list when Show attendance list? is accepted attendees;
- Meet profiles when the event enables them, the viewer is signed in, and the viewer can see the attendee list.
An acceptance decision therefore affects both attendance and information visibility.
Capacity and event end
Signup target does not limit registration. The host accepts or rejects requests independently of that planning number.
An exact-date event is over after its configured end time in the event location timezone. New registration and cancellation are then disabled. The time-to-be-announced modes do not become ended automatically.
Notifications
Submission persists the registration and starts its registration message. Changing a registration to Accepted or Rejected persists the decision before starting the corresponding status message. Accepted attendees also enter ticket delivery when the event has Send tickets after signup/confirmation? enabled. The saved registration state remains authoritative if background delivery is delayed or fails.