> 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/share-guest-tickets.md). # How Members Share Guest Tickets When a member buys multiple tickets to an event, they can share the extras with a guest. The guest receives the ticket by email or SMS and presents it at the door. Sharing is **on by default**; the only event-level configuration is whether to disable it. ### Before you begin (Prerequisites) * **Twilio integration**: required for SMS delivery of shared tickets. See: [How to Set Up Twilio](/products/integrations-overview/setup-twilio.md). (Email-only sharing works without Twilio.) * **Require Guest Email / Require Guest Mobile Number settings**: managed by Peoplevine — control what details a member must enter about the recipient. Confirm the values with your Account Manager. See: [Admin Settings Managed by Peoplevine](/products/portal-overview/portal-admin-settings.md). ### The default behaviour * **Sharing is ON by default for tickets.** When a member purchases more than one ticket, the share UI appears in their portal automatically. * The only event-level configuration is to **turn sharing off** if you don't want members to share — you do not need to enable it. * The member remains the ticket holder of record in your CRM. Sharing routes a copy of the ticket to the guest; the member is still the person of record for the transaction. ### What members do 1. The member purchases multiple tickets for an event. 2. After checkout, they see their tickets in the portal **Wallet** with a *Share* action. 3. They open the *Share* flow and enter the guest's contact details. 4. The platform sends the ticket via email and/or SMS based on what the member entered. 5. The guest receives the ticket and can present the QR code at the door. ### What contact details members must enter This is controlled by the **Require Guest Email** and **Require Guest Mobile Number** settings (managed by Peoplevine — contact your Account Manager or Support to change). See: [Admin Settings Managed by Peoplevine](/products/portal-overview/portal-admin-settings.md). | Setting | What members must enter when sharing | | -------------------------- | ---------------------------------------------------------------- | | **Email only** | Guest's email address | | **Phone number only** | Guest's mobile number (SMS delivery requires Twilio integration) | | **Email and phone number** | Both email and phone — both delivery channels used | If your portal is set to *Phone only* or *Email and phone*, **Twilio integration must be active** for the SMS delivery channel to work. See: [How to Set Up Twilio](/products/integrations-overview/setup-twilio.md). ### What appears on the admin guest list When a member shares a ticket, both the member and the guest appear on the event's **ATTENDEE LIST**: * The **guest's name** appears as the attendee on that ticket entry. * The **associated member** is listed underneath the guest name. This means your guest list shows who's actually arriving — not just who paid. You can use **EXPORT GUEST LIST** to download a CSV with both names per ticket for the door team. For event organizers who want **structured guest data** (allergies, seating requests, plus-one names) attached to each share, attach a custom form to the event so members fill it in at registration. See: [How to Gather Additional Information from Members for an Event](/products/control-panel-overview/events-engine-overview/gather-event-info.md). ### Disabling ticket sharing on a specific event If sharing should be off for an event (e.g., a strict member-only experience): 1. Open the event in [**SELL > Manage Events**](https://control.peoplevine.com/events). > **Note (Pro Dash):** Navigate to **SELL > EVENTS > Manage Events**. 2. In the **Customize Event View** section, **turn off the Share button**. 3. Save. With sharing disabled, members cannot pass tickets to a guest from the portal. ### What sharing does *not* do * **It does not transfer ownership.** The member remains the ticket holder of record for refund and CRM purposes. * **It does not collect named-guest data automatically** beyond what the *Require Guest Email / Mobile Number* settings dictate. For richer guest data, attach a form. * **It does not re-validate the guest's membership.** If you need attendance restricted to members only, restrict the event with **Permissions = Active Members** and disable sharing. ### Best Practice * **Decide club-wide on the email/phone setting** rather than per event. The setting affects all sharing across the portal — confirm it once with your Account Manager. * **For events where you need named guest data** (security lists, dietary, seating), attach a form at end of registration. The form responses can be exported alongside ticket data for one consolidated guest sheet. * **For strict member-only events**, disable Share *and* set Permissions to *Active Members Only* — both are needed, since Share alone doesn't validate the recipient. * **Train the front desk on the guest-list rendering.** When a guest arrives, they show on the list with the member listed underneath — that's the correct mapping, not a duplicate entry. ### What Happens Next * **On the member side**: Member shares ticket → guest receives the ticket via email/SMS → guest presents QR at the door. * **On the admin side**: Guest list shows the guest as the attendee with the member named underneath; export reflects both. * **Next step**: [How to Gather Additional Information from Members for an Event](/products/control-panel-overview/events-engine-overview/gather-event-info.md) · [How to Manage Event Registrations](/products/control-panel-overview/events-engine-overview/manage-registrations.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/share-guest-tickets.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.