Registrations

People register for an event on its event page. They pick a ticket on the ticket card and choose its button (Register for a free ticket and Get Tickets for a paid one, by default). Checkout opens on its details step, which asks for a Quantity, Full name and Email, then the event's custom questions and, when the event attaches it, the dietary and accessibility inquiry. The name and a valid email are required, and an attendee who's signed in has them filled in.

The last button on the details step decides what happens next:

• Complete registration: for a free ticket. Events records a free order and a Confirmed registration.
• Continue To Payment: for a paid ticket. The attendee pays through Stripe, and Events records a Confirmed registration once the payment goes through.
• Request to register: when the event requires approval. Events records a Pending registration and takes no payment until you approve it.

The button reads Continue instead when more steps follow, such as seats, add-ons or a terms review. Each registration takes as many seats as the quantity chosen. For ticket types, prices and the rest of checkout, see Tickets.

By default, Registrations appears in the sidebar for the Owner, Admin, Manager and Member roles. To change who sees it, see Roles and permissions.

To register someone yourself, for a comp, a VIP or a phone sign-up, choose Registrations → RSVPs in the sidebar, then Add Registrant. Full name and Event are required: Events won't add the registrant without them.

• Email and Phone: optional. Approval emails go to the email address.
• Event: the event they're registering for. When you add someone from an event's own registrations, the event is already set.
• Status: Confirmed, Pending, Waitlisted, Checked-in, Declined or Cancelled. New registrants are Confirmed.
• Party size: how many seats the registration takes, the registrant included. It starts at 1.
• Dietary needs and Accessibility needs: optional notes that feed the needs report in Dietary & Accessibility.

Choose Add Registrant to save. The registration's source is Organizer. Adding someone doesn't check the event's capacity, doesn't create an order or a ticket, and doesn't email them.

A registration is one person's place at one event. It's separate from an order: every completed checkout on the event page records both, an approval request records only the registration, and a registrant you add by hand has no order. Changing a registration never changes an order, and refunding or canceling an order doesn't change its registration.

Every registration has one of six statuses:

• Confirmed: has a place at the event.
• Pending: waiting for your decision in Approval Gates.
• Waitlisted: in the event's queue in Waitlist, where its position shows as #1, #2 and so on.
• Checked-in: marked as arrived.
• Declined: their request was turned down.
• Cancelled: no longer coming. Events never sets this status on its own.

Confirmed and Checked-in registrations take seats: each one counts its party size, which is the quantity chosen at checkout or the Party size you set when adding someone by hand. Seats are what the registration screens compare with the event's capacity.

The source says where a registration came from: Online (the event page), Organizer (added by your team) or Kiosk (the check-in kiosk's Register option). The guest list in Guests is built from registrations; see Guests.

Choose Registrations → RSVPs in the sidebar to see every registration in the project. Switch between two views at the top:

• By Event (the default): a card for each event that has at least one registration, with its date, format and how many registrations are Confirmed, Pending, Waitlisted and Checked-in. The right side shows seats filled out of the event's capacity, or No limit, and a Full or Over capacity badge marks events at or past capacity. Events with the most Pending and Waitlisted registrations come first, then the busiest. Search matches event names.
• All People: every registration, newest first, with the person, event, source, registration date and status. A number beside a name shows how many extra seats the registration takes. Search matches names, emails and event names. Click a row to open its details.

The lists show 60 events or 100 people at a time, with a Show more button at the bottom for the rest. Click an event card to manage that event's registrations.

Export downloads every registration in the project as a CSV file, whatever view or search you're on, with each person's name, email, event, status, source, party size, dietary and accessibility needs, and registration date.

Waitlist, Approval Gates and Capacity Limits depend on RSVPs, and Dietary & Accessibility depends on Registration Forms. To hide RSVPs or Registration Forms from your own sidebar under Settings → Navigation, hide the entries that depend on it first; see Sidebar navigation.

Click an event card in Registrations → RSVPs to open that event's registrations. The header shows seats filled out of capacity, and the tabs narrow the list: All, Pending, Confirmed, Waitlist and Checked in, each with its count. Search matches names and emails, and All Events at the top goes back.

• Approve on a Pending row and Promote on a Waitlisted row confirm that registration.
• Each row's ⋯ menu has View details, Check in (for Confirmed registrations), Move to waitlist and Remove.
• Select rows with their checkboxes, then choose Confirm or Waitlist to change them all at once, or Clear.

Click a row to open its details: event, source, registration date, party size, phone, waitlist position, dietary and accessibility needs, and answers to custom questions under Form answers. Change the status from the Status menu, or with the buttons at the bottom: Approve and Decline, Check in, or Promote.

Every change saves straight away. Approving here doesn't email the attendee: approve in Approval Gates for that. Check in only changes the status and doesn't record an admission in Check-in. Remove asks you to confirm first, and a removed registration can't be restored from Events.

Export downloads the registrations in the current tab and search as a CSV file, and Add Registrant adds someone to this event.

When checkout finishes, the attendee sees a confirmation screen that depends on the outcome:

• You're going! for a confirmed registration, with the ticket and quantity, the date and venue, their email and the order number.
• Registration received when the event requires approval, with the status Pending review.

What arrives by email depends on how they registered:

• A paid order gets its tickets by email once the payment goes through. See Tickets.
• A free registration gets no email from Events, so the confirmation screen is its only confirmation.
• A request waiting for approval gets no email until you approve it in Approval Gates.

When dietary and accessibility requests are turned on for the project and for the event, the confirmation screen also has a Dietary or accessibility need? box, where the attendee writes a request and chooses Send request.

RSVP options set whether an event's registrations need approval and how many people it takes. In the event editor, open RSVP Options, under Registration. Each switch saves as you change it, and Maximum attendees saves when you leave the field.

• Require approval: every registration from the event page becomes a request. The last checkout button reads Request to register, no payment is taken, and the registration waits as Pending in Approval Gates. It's off to start with.
• Limit capacity and Maximum attendees: the event's capacity, the same number as the capacity you set when creating the event and in Capacity Limits. Turning on Limit capacity sets 100 when the event has no capacity yet, and turning it off removes the limit. Once tickets sold reach it, the event page shows Sold out.
• Enable waitlist: shows One entry per guest on the waitlist. The event page doesn't put anyone on the waitlist itself: when the event is full, it shows Sold out.
• One entry per guest on the waitlist: stops someone whose email is already on the event's waitlist from registering or buying again. Checkout tells them they're already on the waitlist.

Enable RSVPs, at the top, only shows or hides these settings. Turning it off doesn't change the event page, and a setting that's already on, such as Require approval, stays in effect.

The other settings in the section (Allow "Maybe" responses, Allow changes & cancellations, RSVP deadline, Allow plus-ones and its options, Show who's going and Send confirmation email) are saved with the event but don't change the event page or checkout. A deadline doesn't close registration, and no confirmation email is sent.

Custom questions are what checkout asks each attendee after their name and email. To add one, open the event in the event editor, open Custom Questions and choose Add question. Type the Question label, pick an Answer type (Short text, the default, Paragraph, Dropdown, Checkboxes or Number), turn on Required question if it must be answered, and choose Add question. Only the label is required.

Every change in this section saves on its own. Use the arrows to reorder questions and each question's Required switch to change whether it must be answered. The trash icon removes a question straight away, without asking. To change a question's label or type, remove it and add it again.

On the event page:

• Short text and Number are one-line boxes, and Paragraph is a larger box.
• Checkboxes is a single tick box, and Dropdown is a text box: there's no list of choices to pick from.
• Questions labeled Name, Full name, Email or E-mail are skipped, because checkout always asks for those.
• Checkout won't continue until every required question is answered.

An answer to a question whose label mentions diet or allergies is saved as the registration's dietary needs, and one whose label mentions accessibility, mobility or disability as its accessibility needs. Other answers appear under Form answers in the registration's details.

A new event's list starts with Full name, Dietary requirements, T-shirt size and How did you hear about us?, but checkout asks none of them until you first add, remove, reorder or change a question. The event page also lists the questions in a card headed At registration; to rename it, choose the name beside Shown on your page as. Checkout asks only the questions in this section: forms built under Registrations → Registration Forms aren't attached to any event.

In the event editor, open Registration Settings, under Registration. Both switches save as you change them.

• Show tickets remaining: on to start with. The event page shows how many tickets are left, or that the event is sold out.
• Require approval: adds an Approval Required notice to the ticket card when the event page uses the Luma layout. It doesn't hold registrations for approval: to do that, turn on Require approval in RSVP Options.

Choose Registrations → Approval Gates in the sidebar to see every event with registrations waiting for a decision, each with how many are pending. Sort by Most pending (the default), Fewest pending or Event date, or alphabetically by name, and search by event name. Click an event to see its requests, oldest first, with each person's email, request date, party size, dietary and accessibility needs, and up to three of their answers.

• Approve confirms the registration straight away.
• Decline asks you to confirm, then sets the registration to Declined.
• Approve all and Decline all act on every pending request for the event, and ask you to confirm first. Approve all is also on each event's row in the list.

Approving here emails the attendee a link back to the event page, where checkout opens with their name and email filled in so they can finish registering, or pay for a paid ticket. Until they do, they have a Confirmed registration but no order or ticket. Approval doesn't check capacity, so an approved attendee can find the event sold out when they come back.

The email goes only to registrations with an email address, and only while Registration approved is on under Settings → Notifications; see Settings. Approving from RSVPs confirms without sending it. Events doesn't email declined attendees, so let them know yourself. To reverse a decision, change the registration's status in RSVPs.

Choose Registrations → Waitlist in the sidebar to see every event that has someone waiting, with how many are waiting and how many seats are open (capacity minus seats taken), or full. Sort by Most waiting (the default), Fewest waiting, Most open spots or Event date, or alphabetically by name, and search by event name.

Promote on an event's row, or Promote next once you click into the event, confirms the person at the top of the queue and moves everyone else up a place. Both need an open seat. An event with no capacity limit always shows as full here, so promote its waitlisted people from RSVPs instead, where Promote confirms the person on that row.

An event's own view lists its queue in order, with each person's position, email and the date they joined. People you move to the waitlist from RSVPs get no position number and queue after everyone who has one.

Events promotes people only when you do: the settings under Rules are saved but don't promote or email anyone. A promoted person gets a Confirmed registration, but no email, order or ticket.

The event page never puts anyone on the waitlist: when tickets sold reach capacity, it shows Sold out. People join a waitlist when you set their status to Waitlisted, or when they register at the check-in kiosk after the event's seats, plus any overbook buffer, are full.

An event's capacity is how many people it takes, and 0 means no limit. Set it when you create the event, in the event editor's RSVP Options, or in Registrations → Capacity Limits: click an event, change Capacity and Overbook buffer (extra seats beyond capacity) in Adjust capacity, and choose Save.

Capacity Limits lists every event with its seats taken out of capacity plus buffer, how full it is, and its buffer. At capacity counts events that are full or over, Total seats adds up every event's capacity, and Avg. fill averages the fill of events that have a limit. Sort by Fullest first (the default), Emptiest first, Most seats left or Largest capacity, or alphabetically by name, and search by event name.

Capacity limits sales and registrations in different ways:

• The event page counts tickets sold, not registrations, and shows Sold out once they reach the capacity. It doesn't use the buffer.
• Door sales and the check-in kiosk can go past capacity, up to capacity plus the buffer.
• Registrations you add by hand, approve or promote aren't checked against capacity, and don't count as tickets sold.

The fill on Capacity Limits, RSVPs and Waitlist counts the seats taken by Confirmed and Checked-in registrations.

Guidelines answer attendees' dietary and accessibility questions before they register, like where the step-free entrance is. To add one, open the event in the event editor, open Dietary & Accessibility, under Location, and choose Add guideline. Pick a Category (Dietary, the default, or Accessibility), type the Guideline, and optionally a detail to show under it. Use the arrows to reorder guidelines and the trash icon to remove one.

Nothing reaches the event page until you choose Save guidelines, and a guideline with no text isn't shown. The event page lists the venue's guidelines first, then the event's, in a card headed Dietary & Accessibility. To rename the card, choose the name beside Shown on your page as at the top of the section and type up to 60 characters.

The section's Requests card has Enable post-purchase requests, which saves as you change it. While it's on, and requests are turned on for the whole project in Registrations → Dietary & Accessibility, the confirmation screen at the end of checkout lets attendees send you a dietary or accessibility request.

The needs report gathers every registration with dietary or accessibility needs, for catering and venue planning. Choose Registrations → Dietary & Accessibility in the sidebar; it opens on the Needs report tab. Registrations that were declined or canceled are left out.

• The figures across the top count Registrations with needs (with their total heads, adding up party sizes), Dietary requirements and Accessibility requests.
• Dietary breakdown counts the registrations whose dietary needs mention Vegetarian, Vegan, Gluten-free, Nut allergy, Halal, Kosher or Dairy-free. Only requirements someone has are shown.
• Inquiry responses counts how many people picked each option in the dietary and accessibility inquiry, once there are answers.
• The table lists each registrant with their event, dietary and accessibility needs, party size and registration date.

The event filter, All Events to start with, narrows everything on the tab. Search matches names and needs, and narrows only the table. The export icon beside the tabs downloads the table's rows as a CSV file with each person's name, email, event, needs and party size.

Needs come from custom questions about diet, allergies, accessibility, mobility or disability, and from the Dietary needs and Accessibility needs fields when you add a registrant by hand.

Requests let attendees message you about a dietary or accessibility need once they've registered. To turn them on, choose Registrations → Dietary & Accessibility, open the Requests tab and turn on Enable Dietary & Accessibility Requests. The switch covers the whole project, is off to start with, and saves as you change it. Each event also has to opt in with Enable post-purchase requests in the event editor's Dietary & Accessibility section.

Request prompt is optional text shown over the attendee's message box, and it saves when you leave the field. Attendees see the box on the confirmation screen at the end of checkout, write their request and choose Send request. It arrives with the name and email they gave at checkout.

The Requests tab lists requests newest first, with who sent each one, the event, the request, its status (Open or Resolved) and when it arrived. Filter by event and status, or search names, emails and messages. Each row's ⋯ menu has Mark resolved or Reopen, and Delete, which asks you to confirm first and can't be undone. Events doesn't tell you when a request arrives, so check the tab. The export icon beside the tabs downloads the requests shown as a CSV file.

The inquiry is a set of multiple-choice questions, such as dietary preferences, that checkout asks on every event that attaches it. You build it once for the project: choose Registrations → Dietary & Accessibility, open the Inquiry tab and choose Add question.

• Question label: the question. It starts as Untitled question.
• Type: Single choice (radio), the default, or Multiple choice (checkboxes).
• Options: the answers to pick from. Choose Add option for each one. A question keeps at least one option.
• Required: checkout won't continue until the question is answered.

Use the arrows to reorder questions and the trash icon to remove one. Under Introduction, an optional Heading and Description appear over the questions in checkout. Nothing saves until you choose Save inquiry, which drops blank options and any question without a label or an option.

To ask the inquiry on an event, open the event in the event editor, open Tickets, and turn on Attach Dietary & Accessibility inquiry. It saves on its own and lists the questions checkout will ask. The answers are counted under Inquiry responses in the needs report.