Event Management Route Map

Use This Reference Carefully

Use this guide when event setup, attendee operations, staff work, payment-adjacent tasks, public pages, or closeout records need a controlled path. In this guide, Event Management Route Map narrows that work to reference map of Event Management dashboard routes, aliases, and query-ID behavior. Because this is a reference page, read it as part of the Event Management learning path rather than as an isolated checklist.

Event records become real-world instructions: what attendees see, what staff do, what money or inventory must reconcile, and what future organizers inherit. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What This Reference Collects

This page is for checking details. Use it to confirm names, routes, records, fields, or certification points before relying on memory. The intended readers are Support leads and Event leads. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /rego and /rego/events/manage?id=:eventId.
• Records or contracts involved: Route manifest.
• Main care point: Watch for changing one part of the event without checking attendees, staff, finance, communications, public information, and closeout records.
• Proof worth keeping: event ID, dashboard state, public page, attendee record, payment or refund state, check-in count, roster note, export, and reviewer signoff.

How To Find The Right Entry

1. Search for the exact name or route: Begin by naming the Event Management situation, the owner, and the exact item involved in Event Management Route Map.
2. Read the surrounding note, not only the matching line: Use /rego and /rego/events/manage?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Compare the reference with the live screen, file, or service evidence: Keep Route manifest in view so the work stays tied to the records or contracts it can affect.
4. Save the evidence that proves the entry was checked: Before handing off, save proof such as event ID, dashboard state, public page, attendee record, payment or refund state, check-in count, roster note, export, and reviewer signoff so the next operator can see what changed and why it was safe to continue.

Confirm The Reference Still Matches Reality

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on attendees, staff, money, public pages, communications, and post-event records.
3. Proof is findable: The handoff points to evidence that the next operator can see what changed and why it was safe to continue.

End-to-end operator runbook

Use this numbered runbook when you need to operate this area without getting stuck. Read the purpose of each step, do the action in order, and use the final sentence as the checkpoint before continuing.

1. Step 1 - Choose the right path. Use this reference when you need to confirm a route, role, record, or certification expectation before acting. This anchors the work to the correct scope before any record changes.
2. Step 2 - Confirm scope and records. Find the dashboard surface or record type involved in the current task. Pause here and confirm the attendee, staff, money, and public-page impact still matches the event plan.
3. Step 3 - Do the operating action. Compare what you see in /rego, /rego/events/manage?id=:eventId with the expected access, state, and records described here. This keeps the event state understandable before another setting changes.
4. Step 4 - Verify the result. If something does not match, stop the workflow and capture the route, event/report ID, user role, and visible error state. The next operator should be able to see why this step was taken.
5. Step 5 - Hand off remaining work. Return to the related operating guide after the reference question is answered. This leaves a handoff trail another operator can understand.

Entry routes

• /rego
• /rego/events
• /rego/events/new
• /rego/regos
• /rego/events/manage?id=:eventId

Event-scoped manage routes

Every route below depends on ?id=:eventId. The dashboard must keep the same event ID when staff move between pages.

Route	Surface group
/rego/events/manage/details?id=:eventId	Details and public event information
/rego/events/manage/rego-config?id=:eventId	Registration configuration
/rego/events/manage/dealers-den?id=:eventId	Dealers Den settings
/rego/events/manage/conditions-of-entry?id=:eventId	Conditions of Entry
/rego/events/manage/offline-snapshot?id=:eventId	Offline check-in snapshot
/rego/events/manage/offline-snapshot-history?id=:eventId	Offline snapshot history
/rego/events/manage/payments-config?id=:eventId	Payment configuration
/rego/events/manage/notification-config?id=:eventId	Notification configuration
/rego/events/manage/google-wallet-config?id=:eventId	Google Wallet configuration
/rego/events/manage/check-in?id=:eventId	Check-in workspace
/rego/events/manage/regos?id=:eventId	Registration orders
/rego/events/manage/registrants?id=:eventId	Registrants and attendees
/rego/events/manage/dealers-den-applications?id=:eventId	Dealers Den applications
/rego/events/manage/dealers-den-regos?id=:eventId	Dealers Den registrations
/rego/events/manage/upgrades?id=:eventId	Registration upgrades
/rego/events/manage/refunds?id=:eventId	Refund handling
/rego/events/manage/transfers?id=:eventId	Transfer handling
/rego/events/manage/waitlist?id=:eventId	Waitlist handling
/rego/events/manage/human-resources?id=:eventId	Human Resources overview
/rego/events/manage/volunteer-positions?id=:eventId	Volunteer positions
/rego/events/manage/volunteer-applications?id=:eventId	Volunteer applications
/rego/events/manage/staff-roster?id=:eventId	Staff roster
/rego/events/manage/live-shift-tracker?id=:eventId	Live shift tracker
/rego/events/manage/activities?id=:eventId	Activities
/rego/events/manage/submissions-review?id=:eventId	Submission review
/rego/events/manage/approved-submissions?id=:eventId	Approved submissions
/rego/events/manage/communications?id=:eventId	Attendee communications
/rego/events/manage/attendee-coupons?id=:eventId	Attendee coupons
/rego/events/manage/affiliates-tracking?id=:eventId	Affiliate tracking
/rego/events/manage/rego-analytics?id=:eventId	Registration analytics
/rego/events/manage/finance-analytics?id=:eventId	Finance analytics
/rego/events/manage/settlements?id=:eventId	Settlements and reconciliation
/rego/events/manage/inclusion-claim?id=:eventId	Inclusion claim
/rego/events/manage/inventory-analytics?id=:eventId	Inventory analytics
/rego/events/manage/inventory-tracking?id=:eventId	Inventory tracking
/rego/events/manage/point-of-sales?id=:eventId	Point of Sales
/rego/events/manage/config?id=:eventId	Moved or compatibility config route
/rego/events/manage/payments?id=:eventId	Moved or compatibility payment route
/rego/events/manage/pos?id=:eventId	Moved or compatibility POS route
/rego/events/manage/staff-subsidies?id=:eventId	Moved staff subsidy route

Alias notes

payments, pos, config, and staff-subsidies exist as compatibility or moved-page surfaces. They still need safe route behavior and preserved event IDs.

Public-facing routes

Public pages are not partner dashboard pages, but they are affected by dashboard setup.

Route	What attendees see
/events/:slug	Public event details and registration entry points
/events/dealers-den/:slug	Public Dealers Den information and application entry points

Public routes should match the event record, registration settings, Dealers Den settings, Conditions of Entry, payment instructions, and any public visibility controls.