Upgrades

Overview

Upgrades is the review queue for attendees who request a higher tier or additional items after their original registration. Approval can affect capacity, payment amount, Discord/Telegram/ZEP access, inclusions, and check-in expectations.

Dashboard route

/ems/manage/upgrades?id=:eventId

The page loads upgrade requests from /api/events/:eventId/rego-upgrades. It also loads event tiers and add-ons so requested changes can be shown by name instead of only by ID.

Table controls

Control or field	Type	Options or behavior	Operational impact
Search	Search input	Filters by rego ref, attendee label, attendee email, current tier, requested tier, current add-ons, and requested add-ons.	Finds upgrade requests without changing them.
Status filter	Dropdown	All statuses, Pending review, Awaiting review, Declined, Expired, Finalized, Cancelled.	Separates requests that need action from historical outcomes.
Count badge	Generated badge	Shows total loaded upgrade requests when present.	Quick volume signal for the queue.
Details	Row button	Opens the details modal.	Used for inspection without deciding.
Notify	Row button	Opens targeted attendee notification composer for that request.	Sends a manual update about the upgrade request.
Actions	Row button	Visible only when request status is pending_review or accepted.	Opens approval/decline workflow.

Request row fields

Field	What it shows	Why it matters
Ref	Rego reference.	Precise support identifier.
Attendee	Attendee label and email.	Confirms who requested the upgrade.
Status	Pending review, Awaiting review, Declined, Expired, Finalized, or Cancelled.	Shows whether staff can act or only inspect history.
Requested	Request timestamp.	Useful for queue order and payment-window review.
Request	Current tier/add-ons, requested tier/add-ons, price difference, and Direct pay or Manual review badge.	Shows what would change if accepted.

Details modal

Field	Meaning	Check before action
Status chip	Current upgrade request state.	Only pending/accepted requests should be acted on.
Mode chip	Direct pay or Manual review from Rego Config.	Direct-pay requests may already have payment flow expectations; manual-review requests need staff decision first.
Current tier / Requested tier	Tier movement requested by attendee.	Confirm capacity and entitlement differences.
Current add-ons / Requested add-ons	Add-ons before and after the request.	Confirm stock, access, and fulfillment impact.
Payment status	Payment state attached to the request/rego.	Do not approve without understanding payment next steps.
Price difference	Amount the upgrade changes.	Confirm before telling attendee to pay or finalizing.
Requested/Reviewed timestamps	Audit timing.	Helps explain whether a request is stale, expired, or already handled.
Organizer note	Saved staff note when available.	Read prior decisions before adding a new one.

Action modal

Control	Type	What it does	Check before using
Staff note	Textarea	Optional note saved to the request audit trail.	Add context for capacity, payment, stock, or attendee follow-up.
Approve request	Submit button	Sends decision: accept to the review endpoint.	Confirm tier capacity, add-on stock, entitlements, and payment mode.
Decline request	Button	Sends decision: decline to the review endpoint.	Record why the request should not move forward.
Cancel/close	Button/backdrop/Escape	Leaves the request unchanged.	Use when the wrong request is open.
Error alert	Generated alert	Shows API/review errors.	Do not retry blindly; fix the cause or reload first.

Flowchart context

Create an Event configures upgrade availability in Rego Config. Active Event Workflow reviews this page during daily registration operations.

Common mistakes

Do not approve an upgrade only because payment is possible. Confirm tier capacity, included items, and access entitlements before accepting.