Registration detail

Click any row in the Registrations tab and a detail sheet slides in from the right. The sheet covers everything attached to that registration: the purchaser's identity, every ticket in the order, per-ticket attendee data and custom question answers, order financials, and your internal notes.

Most fields are editable inline. You don't need to open a separate form — click a value, type, and press Enter or Tab away to save.

Opening the sheet

From the Registrations tab, click any registration row. The sheet opens over the page — nothing navigates away. Close it with the X button in the top-right corner, or click outside the sheet.

The header and three-dot menu

The sheet header shows the registrant's full name, a status pill (Confirmed, Pending, Awaiting approval, Waitlisted, Cancelled, and so on), and a Checked in pill when the registration has a check-in timestamp. Below the name, the subtitle shows the registrant's email address and when they registered.

The three-dot menu next to the close button contains registration-level actions. Currently it offers one option: Cancel registration. This option is disabled when the registration is already cancelled or refunded. Cancelling the registration marks every attached ticket cancelled; Stripe refunds are handled separately.

The Tickets tab

The Tickets tab is always present. It lists every ticket in the registration as a card. Each card shows:

• Ticket code and status pill — one of Cancelled, Transferred, Transfer pending, Claimed, or Unclaimed.
• Attendee name — click to open an edit popover for first name, last name, and email.
• Ticket type and price tier (when the event uses price tiers) — click to open a reclassify popover.
• Price paid.
• Claimed timestamp (when claimed).
• Checked in badge with timestamp (when checked in).
• Badge printed badge (when the badge has been printed at the kiosk).

When a transfer is pending, the card shows the recipient's details — name and email — alongside a Sent by line showing who initiated the transfer and when the claim link expires.

Click a ticket card to open the Ticket Detail Rail in the right aside. The selected card gets a highlighted border so you can see at a glance which ticket the rail refers to. Click the same card again, or use the X in the rail header, to return to the registration-level Details Rail.

Per-ticket actions

Each ticket card has a three-dot menu. The options available depend on the ticket's current state.

When no transfer is pending:

• Transfer ticket — sends the recipient an email with a one-tap claim link. Disabled if the ticket is already cancelled or checked in.
• Claim on behalf — marks the ticket as claimed and sets the attendee identity you provide, without sending an email. Disabled if the ticket is cancelled.
• Refund… — fires an immediate Stripe refund. Pre-fills the amount with what the ticket cost; lower it for a partial refund. Only enabled when price_paid > 0.
• Cancel ticket — marks this ticket cancelled without touching the rest of the registration. Does not trigger a Stripe refund; use Refund… separately if money needs to come back.

When a transfer is pending, the menu shows only one option:

• Cancel transfer — voids the pending transfer. The recipient's claim link stops working and the ticket returns to its prior attendee.

Ticket Detail Rail

Clicking a ticket card swaps the right aside from the registration-level Details Rail to the Ticket Detail Rail. The rail is headed by the ticket code and a close button. Below that, four sections:

• Identity — first name, last name, email. All three are editable inline (click-to-edit). Disabled for cancelled tickets.
• Overview — ticket type (click-to-edit reclassify), status, price paid, claimed timestamp, checked-in timestamp, and created date.
• Pending transfer — appears only when a transfer is pending. Shows the recipient email, who initiated the transfer, and when the claim link expires.
• Questions — custom per-ticket question answers. Each answer is editable via a click-to-edit popover. If the ticket type has no per-ticket questions, this section shows a placeholder.
• Documents — files the attendee uploaded as part of intake. Shows filename, document label, file size, and submission date.

Registration-level details rail

When no ticket card is selected, the right aside shows the Details Rail — registration-level information grouped into five sections.

• Identity — first name, last name, email of the purchaser. All editable inline.
• Overview — registered timestamp, checked-in timestamp, total ticket count (with unclaimed count if any), registration path (editable if the event has paths configured), and confirmation email sent timestamp.
• Preferences — email opt-in toggle (editable) and a Revoke marketing consent action.
• Order — subtotal, discount (with code if one was applied), tax, total, payment status, and the Stripe Payment Intent ID for paid orders.
• Internal notes — a free-text textarea, editable inline. Notes are visible only to your team and never shown to the registrant.

Editing inline fields

Most values in both rails are click-to-edit. Click the value, and an input appears in place. Press Enter or click away to save. Press Escape to discard the change. If the value hasn't changed from what was loaded, clicking away does not trigger a save.

Some fields open a popover instead of an inline input — ticket type/tier reclassification and per-ticket question answers both work this way. Make your changes inside the popover and click Save to commit. The Save button is disabled until you've changed something.

Fields on cancelled tickets are locked and cannot be edited.

Internal notes

The Internal notes textarea at the bottom of the Details Rail is a free-form scratchpad for your team. Use it to record anything you'd want a colleague to see at a glance — special accommodations, unusual circumstances, follow-up items.

Click anywhere in the textarea to start editing. Changes save when you click outside the field. Notes are operator-only and are never surfaced to the registrant.

Notes tab

A Notes tab appears in the left panel alongside the Tickets tab only when the registration has at least one of the following: an approval reason, a cancellation reason, a cancellation timestamp, or internal notes. If none of these are present, the tab strip is hidden entirely and Tickets appears as a static label.

The Notes tab displays those values in a read-only table: Approval reason, Cancellation reason, Cancelled at, and Internal notes. These are the same internal notes you edit from the Details Rail — the Notes tab is a secondary surface for reading them alongside the other system-recorded reasons.