Regos

Overview

Regos is the main attendee registration operations page. It lets staff review attendee records, payment state, tier and add-on selections, registration status, communication actions, and exception handling.

Dashboard route

/ems/manage/regos?id=:eventId

The page loads event tiers and add-ons first, then loads attendee regos from /api/rego/event-regos/:eventId. It requires a signed-in dashboard session and an event ID.

Table controls

Control	Type	What it does	Operational impact	Check before using
Search	Search input	Filters by rego ref, attendee display name, email, legal name, date of birth, fursona name, payment reference, payment method, tier name, and add-on names.	Narrows the visible table only; it does not change records.	Clear search before reporting totals or missing records.
Payment	Status filter dropdown	Filters by payment status. Options are All payment statuses, Pending, Submitted, Confirmed, Failed, Refunded, and Onsite, each with counts.	Helps isolate records needing finance or onsite handling.	Confirm the filter is not hiding other payment states before acting in bulk.
Select visible	Checkbox	Selects or clears all currently visible regos.	Drives bulk payment updates for the filtered/search result set.	Make sure search and payment filters show exactly the intended records.
Row checkbox	Checkbox	Adds or removes one rego from the selected set.	Lets staff build a smaller bulk-update group.	Confirm each selected row’s attendee, ref, and status.
Bulk payment update	Dropdown	Chooses the status to apply to selected regos. Options are Pending, Submitted, Confirmed, Failed, Refunded, and Onsite.	The selected status is applied one-by-one through /api/regos/:id/payment-status.	Do not bulk-confirm without verifying payment policy and proof scope.
Apply	Button	Applies the selected bulk status to selected rows.	Changes payment status for multiple attendee registrations.	Stop if no selected count, no action, or filters are uncertain.

Row fields and actions

Field or action	What it shows or does	Why it matters
Ref	Rego reference and payment-status badge.	The precise support identifier and current payment state.
Attendee	Display name, legal name when available, email, fursona name, DOB, payment ref, tier, add-ons, and submitted date.	Gives staff enough context to identify the attendee and selected products.
Staff Rego badge	Appears when staff subsidy amount is greater than zero.	Identifies subsidized staff registrations.
Gift source	Gift-redemption regos use the receiver’s attendee details and may carry gift source metadata.	Once redeemed, manage the rego under the same refund, transfer, upgrade, payment, and check-in rules as other attendee regos.
DOB	Date of birth in its own column on larger tables.	Helps age and identity review.
Tier	Tier name resolved from event Rego Config.	Confirms access level and included items.
Payment	Payment reference summary.	Helps match bank/payment proof to the row.
Submitted	Submission time.	Useful for order-of-arrival and support review.
Details	Opens attendee detail modal.	Use for full profile, rego, fursona, and ref-sheet review.
Payment	Opens payment quick view.	Use for payment status/method/reference/proof checks.
Notify	Opens attendee notification composer for the selected rego.	Use for targeted attendee communication without leaving the page.
Actions	Opens status/email/follow-up action modal.	Use for record-changing payment status updates or attendee emails.

Details modal

Section	Fields	Operational use
Header	Profile photo or initial, display name, email, username, rego ref, tier, staff rego chip, and status chip.	Confirms the exact attendee before staff review private details.
Rego details	Reference, staff rego badge, tier, add-ons, payment status, payment method, payment reference, Pawsport number, submitted at, confirmed at, last updated.	Main record check before changes, check-in support, or finance review.
Attendee profile	Display name, legal name, preferred name, username, email, contact number, date of birth, pronouns, address fields, terms accepted.	Identity, contact, and conditions acceptance context.
Fursona profiles	Saved fursonas, species/pronouns, and ref-sheet download buttons.	Used when staff need profile or reference-sheet context.

Payment quick view

Field or action	What it shows	Check before using
Payment status	Current payment state.	Compare against event confirmation policy.
Payment method	Method submitted by attendee.	Match with expected provider or onsite process.
Payment reference	Attendee-entered reference.	Compare against actual account or proof.
Total paid	Grand total and currency from rego totals.	Confirm amount before marking confirmed/refunded.
Open payment proof	Link shown when proof exists.	Review only relevant proof and avoid sharing private data.
No payment proof uploaded	Empty state.	Do not assume payment exists without other evidence.

Actions modal

Mode or field	Type	Options or behavior	Operational impact
Update status	Tab button	Shows the Payment status selector and Apply status submit button.	Changes payment status for the selected rego.
Payment status	Select	Choose a status, Pending, Submitted, Confirmed, Failed, Refunded, or Onsite.	Sends a PATCH to /api/regos/:id/payment-status.
Resend rego email	Tab button	Shows explanatory copy and changes submit action to resend.	Sends the original rego receipt email using saved totals, instructions, and current payment status.
Send follow-up	Tab button	Shows markdown-ext message composer and live branded email preview.	Sends a staff-written follow-up to the attendee email on file.
Staff follow-up message	Markdown-ext textarea	Supports the shared markdown-ext set, including tables, code fences, Mermaid, task lists, footnotes, highlight, subscript, and superscript.	Message body for attendee email; required before sending follow-up.
Live preview	Preview pane	Shows subject, from name, reply-to, recipient, iframe preview, and preview status.	Lets staff verify branded attendee-facing wording before sending.
Cancel/close	Button or backdrop/Escape	Closes modal without applying the action.	Use when the selected attendee or action is wrong.

Danger Zone

The Danger Zone is shown only to FPH admin users. Wipe all attendees permanently deletes all attendee regos, POS transaction records, POS line items, Dealers Den applications, and Dealers Den regos for the event. It uses a confirmation dialog and reports the deletion counts after completion.

Flowchart context

Active Event Workflow maps its “Check Rego Screens” and “Resolve registration issues” steps to this page, with related queues on Upgrades, Refunds, Transfers, Gifts, and Waitlist.

Common mistakes

• Do not change a registration status to solve a queue issue without checking payment state. The status may allow entry or trigger attendee expectations.
• Do not use bulk payment update while a search or filter is hiding records from view.
• Do not resend or follow up before confirming the email belongs to the intended attendee.
• Do not use Danger Zone actions outside controlled test or recovery work.