Surfaces
Manage Root Redirect
How the Event Management root route sends operators to the right event workspace.
First created Last updated
Overview
The Manage root route is not an editing page. It is the entry point used when the dashboard needs to open the current event management workspace without naming a specific surface yet.
When an event ID is present, the route sends the operator to Details because Details is the safest landing page for confirming the event name, dates, venue, status, and public-facing identity. When the event ID is missing, the route sends the operator back to the event list so they can choose the correct event.
Because this route has no form fields, there are no editable inputs to audit. Treat it as routing behavior only.
Dashboard route
/ems/manage?id=:eventId
Route behavior
| Route state | What happens | Operator impact |
|---|---|---|
/ems/manage?id=:eventId | Redirects to /ems/manage/details?id=:eventId. | The operator lands on the correct event’s Details page. |
/ems/manage with no event ID | Redirects to /ems. | The operator must select an event before changing records. |
| Invalid, stale, or inaccessible event ID | The destination page shows the relevant loading or access error. | Staff should return to the event list and reopen the event from the sidebar. |
Flowchart context
The Create an Event flowchart uses this route at the “Open Manage Event page” step. The action is only a transition; the actual setup work continues in Details, Payments Config, Rego Config, and the other route-specific surface pages.
Common mistakes
Opening the manage root without an event ID usually means a copied link lost its query string. Reopen the event from the Events list instead of manually typing an ID.