GC Events - Creating Registration Paths (How-to)

What are registration paths?

Registration Paths allow you, as an admin, to tailor the registration experience based on user selections. This enables you to display specific tickets, activities, and add-ons relevant only to certain affiliations, keeping the registration process streamlined and user-friendly.

Path Example Use Case: For a Reunion Weekend, you can offer tickets, activities, and add-ons exclusive to Faculty/Staff, Young Alumni, and Alumni General Admission.

 

To create a registration path, you'll get started with a Restricted Ticket Type.

Next, you'll want to create the specific activities and add-ons that are exclusive to a certain constituent. You can also ask questions that pertain only to folks planning to attend these activities or who purchased the add-on.

By implementing restricted ticket types, activities, and add-ons, you create a tailored registration experience for your constituents. ### Q: Can I force registrants to pick only one of several activities (for example, choose one lunch option)? A: GC Events does not enforce mutual exclusion for activities. Instead, try one of these workarounds: 1. **Option A — Clarify in the activity titles** - Edit each activity title to include a note such as "— Choose 1 only." This communicates expectations without preventing multiple selections. 2. **Option B — Capture the selection with a dropdown custom field** - Create a dropdown custom field at the registration or attendee level. For one answer per registration, add the field in the Registrant section (under **Registrant & Attendee Information**). For one answer per attendee, add the field on the activity page. - Replace the two separate lunch activities with a single activity (if desired) or keep the activities for reporting while enforcing a single selection with the dropdown. > **Tip:** Reusable custom fields are managed under **Events Settings > Reusable Fields**, allowing you to reuse the same dropdown across events. --- ### Q: How do I prevent people outside invited reunion classes from registering for an invitation-only activity (for example, a trustees/reunion reception)? A: Combine ticket-level affiliation restrictions with activity-level restrictions to control access: 1. **Enable affiliation collection** - In the **Details** tab of the event, ensure **Collect Affiliation Data** is enabled. 2. **Create a ticket type for the invited group** - In the ticket editor, add a new ticket (e.g., for specific reunion classes and trustees), check **Restrict Ticket Type**, and select the appropriate restriction mode: - **Based solely on the registrant's affiliation**: Only the main registrant must have the required affiliation. - **Based on the individual's affiliation**: Each registrant and guest must have the required affiliation. (Note: Affiliation must be collected for guests.) - Select the appropriate affiliation values or category. 3. **Restrict the invitation-only activity** - In the **Activities** section of the event edit flow, open the target activity. Under **Activity Restrictions**, check **Restrict Activity Registration**, then choose the ticket type created in step 2. **Outcome:** Registrants and guests without the required affiliation will not see or be able to register for the restricted activity. **Additional tips:** - **Audience Tags vs. Activity Restrictions:** Audience Tags only help filter activities; only **Restrict Activity Registration** blocks registration. - **Activity guest limits** set overall capacity and do not enforce individual limitations. - **Design suggestion:** If all ticket types are restricted by affiliation, consider offering at least one unrestricted ticket type for registrants who do not match any affiliation. - For strict enforcement and reporting, use the combined ticket and activity restrictions along with a dropdown custom field to capture a single selection.