Surfaces
Event Overview and Lists
How to use the Event Management System entry route, event list, and manage overview.
First created Last updated
Overview
The Event Management overview surfaces are the front door into event operations. They help partner teams find the correct event, confirm the event is in the expected state, and move from a high-level list into the individual manage pages where detailed setup and event-day work happens.
Use these pages before changing any event setting. The most common mistake is opening the wrong event, especially when a partner has past test events, draft events, live events, and archived events in the same workspace.
Dashboard routes
/ems/ems/manage?id=:eventId
Entry surfaces
| Surface | What appears there | How operators use it |
|---|---|---|
/ems | Events page with a + New event action and an events list. | Use it to create a new event shell, find an existing event, and open that event’s Details page through the Manage action. |
/ems/manage?id=:eventId | Redirect page for the selected event workspace. | Use it only as a handoff route. It redirects to Details when an event ID exists. |
Events list
The event list is not only a navigation page. It is the first check that the event exists, belongs to the right partner scope, and has the expected lifecycle state. The list may show draft, active, hidden, or archived events depending on the dashboard state and account permissions.
Read the event name, date, and status together. A familiar public name is not enough, because teams often reuse names across yearly events or test copies. If there is an internal name, use it as supporting evidence, not as the attendee-facing title.
| Input or control | What it does | Before using |
|---|---|---|
+ New event | Opens the event creation flow. | Confirm the partner scope, public naming plan, start and end date, and reference prefix before creating a duplicate event. |
| Event row | Shows event identity and status. | Read public name, internal name when available, date, and lifecycle state together. |
| Manage | Opens /ems/manage/details?id=:eventId for that event. | Use only after verifying the row is the correct event. |
| Empty/loading state | Shows whether the list is still loading or has no events. | Wait for loading to finish before assuming an event is missing. |
Manage handoff
| Route state | What happens | Operator impact |
|---|---|---|
| Event ID is present | The manage route redirects to Details for that event. | Every later save uses that event ID, so the identity check on Details matters. |
| Event ID is missing | The manage route redirects back to the Events list. | Select the event from the list instead of guessing an ID. |
| Event ID is inaccessible | The destination page shows the relevant access or loading error. | Return to Events and reopen the event from a visible row. |
How this connects to the setup flow
The create-event flow begins here, then moves into Details, Rego Config, Payments Config, and any optional modules such as Dealers Den, HR, activities, coupons, affiliates, or POS. The overview surface does not replace those pages; it chooses the event shell those pages will modify.
If the flowchart says “Open Manage Event page,” this is the handoff point. The event ID in the URL becomes the anchor for every later setup page. If the wrong event ID is opened, every saved setting after that point goes to the wrong event.
Related actions
Use Create an Event when creating a new shell. Use Manage Root Redirect when a manage link needs to hand off to the current event workspace. Use Details once the event identity has been confirmed.
Operator checklist
- Confirm the partner workspace is correct.
- Confirm the event title and event date.
- Confirm the status is appropriate for the work: draft for setup, active for live registration, hidden for private review, or archived for closed records.
- Confirm the URL or opened row belongs to the intended event ID.
- Open the manage workspace only after the event identity is clear.
Common mistakes
- Editing a previous year’s event because the public name looks familiar.
- Reading a filtered list and assuming missing records do not exist.
- Using a cross-event registration result as proof that a current-event setup is correct.
- Opening a manage page from an old tab after another event has become the active project.