> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/events-engine-overview/members-sign-up-for-events.md). # How Members Sign Up for Events This article describes the **member-side** experience of signing up for events. Use it for member-facing FAQs, training materials, and front-desk talking points. ### What members see Active members find events on the **Events** page of the Member Portal. The page lists upcoming events filtered by the categories your team has configured. Each event shows a card with the title, date, time, summary, and primary image. Depending on the layout your club has chosen, events display either as the default **grid** or as a date-forward **List/Calendar** view for browsing by day — see [Portal Modules and Features — Overview](/products/portal-overview/portal-modules-overview.md). The card also displays one of these states depending on event setup and ticket availability: | State | Card displays | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | Free RSVP event, open | *Register* (or your custom CTA text) | | Ticketed event, on sale | *Buy Tickets* (or your CTA) | | Future on-sale date | *Tickets go on sale \[date]* — if no on-sale date is set but tickets are not yet available, the card shows *Tickets are not yet available* | | Limited availability (≤ 9 left) | *X tickets left* — counter (can be turned off platform-wide) | | Sold out, waitlist available | **Join Waitlist** | | Sold out, no waitlist | *Sold Out* | | External event | Outbound link to your third-party RSVP page | ### How members register #### Free RSVP event 1. The member opens the event detail page. 2. They click **Register**. 3. The system attaches the registration to their CRM profile and issues a **digital (QR) ticket** to their portal Wallet (Account > Wallet > Tickets). If a confirmation email is configured, the member receives it. See: [How to Set Up Event Emails](/products/control-panel-overview/events-engine-overview/setup-event-emails.md). #### Ticketed event 1. The member opens the event detail page. 2. They select a **ticket type** (e.g., *Member* if logged in to a program that grants the member tier; *Non-Member* / *Guest* if available). 3. They choose a **quantity** within the per-order min and max. 4. They proceed to **checkout** and complete payment. 5. On success, the system generates a **digital ticket** with a unique serial number and attaches it to the member's CRM profile. If an event confirmation triggered response is configured, the member receives a confirmation email. The QR code is available in the member portal (Account > Wallet > Tickets). #### Member tier vs non-member tier When an event has multiple ticket tiers with audience restrictions: * An **Active member** in an eligible program sees the *Member* tier (and any restricted-tier they qualify for). The member tier may or may not be discounted — it is simply the tier designated for members. * A **non-member** sees only tiers with **Visibility = Anyone**. If the member is **on a different program** than the event's restricted tier, they see only the tiers they qualify for. ### Sold-out events and waitlist When the event is at capacity: * If a **waitlist is configured**, the card shows **Join Waitlist**. Clicking it routes the member to a form (configured by your team) where they leave their details. When tickets become available, your team can promote the waitlist or send a newsletter to everyone on it. * If **no waitlist is configured**, the card shows *Sold Out* and the member cannot take action. ### After registering * If an **event confirmation** triggered response is configured, the member receives a confirmation email with event and ticket details. See: [How to Set Up Event Emails](/products/control-panel-overview/events-engine-overview/setup-event-emails.md). * Tickets appear in the member's **Wallet** on the portal (Account > Wallet > Tickets) — they can view the QR code, re-open, or share from there. * If a **pre-event reminder campaign** is configured, the member receives a reminder before the event start time. * If a **post-event follow-up campaign** is configured, the member receives a follow-up after the event ends. ### Sharing tickets with a guest Members can share their tickets with a guest by default. The **Require Guest Email** and **Require Guest Mobile Number** portal settings — which control what details a member must enter when sharing — apply to **both event tickets and guest passes**. See: [How Members Share Guest Tickets](/products/control-panel-overview/events-engine-overview/share-guest-tickets.md). ### Cancelling a registration If your team has enabled **Allow guests to cancel their registration** on the event: 1. The member opens **My Schedule** or the event detail page in the portal. 2. They click **Cancel Registration** on their entry. 3. The system releases the ticket back to inventory. 4. If the event was paid, the system **auto-refunds** to the member's original payment method — no staff action is needed. See: [How to Cancel and Refund a Member's Tickets](/products/control-panel-overview/events-engine-overview/cancel-refund-tickets.md). If the option isn't enabled on the event, members cannot self-cancel and must contact your team. ### Sign-in at the door When the member arrives, your front-desk team scans the QR code on their phone. The first scan checks the attendee in. See: [How to Check In Event Attendees](/products/control-panel-overview/events-engine-overview/check-in-attendees.md). ### Best Practice (for clubs) * **Enable *****Allow guests to cancel*** unless your policy requires staff-mediated cancellations. Disabling self-cancel routes every change through your team. * **Configure the portal CTA wording** on the event view to match your tone (e.g., *Reserve Your Spot* instead of *Register*) — set on the event in the Customize Event View section. ### What Happens Next * **For the member**: Tickets appear in the portal Wallet (Account > Wallet > Tickets). If configured, the member also receives a confirmation email, pre-event reminder, and post-event follow-up. See: [How to Set Up Event Emails](/products/control-panel-overview/events-engine-overview/setup-event-emails.md). * **For your team**: The member appears on the event's **ATTENDEE LIST**. Revenue and counts update on the event dashboard. See: [How to Manage Event Registrations](/products/control-panel-overview/events-engine-overview/manage-registrations.md). * **Next step**: [How Members Share Guest Tickets](/products/control-panel-overview/events-engine-overview/share-guest-tickets.md) · [How to Check In Event Attendees](/products/control-panel-overview/events-engine-overview/check-in-attendees.md). *Last updated: 2026-05-24* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.peoplevine.com/products/control-panel-overview/events-engine-overview/members-sign-up-for-events.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.