[P05] Enter an Event
Summary
An entrant enters an event, for themselves or for people they manage, from the event page. The site hands them to the registration portal’s process flow, signed in if they are signed in on the site, or as a guest.
Actor & Context
Actor: Entrant
Frequency: Per entry; peaks when entries open and before they close
Precondition: Registration is open for the event
Entry point: The register button on an event page or elsewhere
Main Flow
-
The entrant clicks the register button.
-
If signed in on the site, the site creates a signed, short-lived link at that moment and sends them to the portal’s process flow for the event, where they arrive signed in with the people they manage.
-
The portal takes them through the event’s enrolment steps and on to payment (P07).
Alternative Flows
-
AF-1: Not signed in, sign-in offered: the site explains what signing in gives them and offers Log in or Continue as guest. A successful sign-in continues straight to the portal signed in; a failed one returns them to the page with the choice offered again.
-
AF-2: Guest: they go to the portal without being signed in.
-
AF-3: Registration closed or not yet open: the button states it and does not hand over.
-
AF-4: Tampered link: the site refuses an event the page does not offer and returns the visitor to the page.
Acceptance Criteria
-
A signed-in visitor arrives in the portal signed in, with their managed people (PS-RG-02)
-
The signed link is never in the page HTML or a cache (PS-RG-02, PS-NF-03)
-
A failed sign-in returns to the page with the choice re-offered (PS-RG-03)
-
The button reflects the registration status (PS-RG-04)
API Surface
The calls below are named by purpose; their exact form is defined in the public site design.
| Call | Purpose |
|---|---|
Site endpoint: build hand-over for page and event |
Signs the link at click time and redirects |
|
Exchanges the signed link for a session |
Design Anchors
-
Public Site Requirements — PS-RG-01 to 06