Registration paths
Audience segments that let you show different ticket sets to different groups — Members vs Guests, Speakers vs Attendees, Internal vs External.
Updated May 26, 2026
Registration paths split your event's registration form into audience-specific views. Each path is a segment — Members, Guests, Speakers — and each one only shows the ticket types you've assigned to it. When the attendee arrives at registration, they pick which group they belong to before they see any tickets.
When to use paths
Reach for paths when the same event has different groups of attendees who see different tickets — and you don't want one group seeing the other group's options. Members get the comp ticket and the workshop add-on; Guests don't see the comp at all and pay full price. Speakers get a Speakers-only registration; Attendees never see it.
Paths are about audience, not pricing. For Early Bird vs Late Registration, don't create two paths — create two ticket types with different sale windows. Paths layer over the same tickets to gate visibility.
Create a path
In your event, open the Paths tab and click Add path. The form asks for:
- Name — required. What attendees see on the path picker ("Members", "Guests", "Speakers").
- Slug — required. Lowercase letters, numbers, and hyphens. Used in the path's direct URL.
- Description — optional. Shown under the path name on the picker, so attendees know which group they fit into.
- Icon — optional. A lucide icon name like
CrownorMic. The registration wizard renders it next to the path name if it recognizes the icon. - Default path — when an attendee lands on the registration page, this path is selected first. Pick whichever is your most common audience.
- Visible — controls whether the path appears on the public picker. Hidden paths remain accessible at their direct URL but do not appear in the picker list.
Assigning tickets to a path
Tickets opt into paths from the ticket's own edit dialog (on the Tickets & Pricing tab). Each ticket lists the paths it can appear on; check the boxes for the ones it belongs to. A ticket can belong to multiple paths.
A ticket with no path assignment at all is visible on every path. That's usually what you want for shared tickets like "General Admission" — assign it to no paths, and it shows up everywhere.
What the attendee sees
If your event has two or more visible paths, the registration wizard adds a path picker as the first step. The attendee chooses a path, then sees only the tickets assigned to that path (plus any path-agnostic tickets). The default path is preselected.
If your event has only one visible path — or none — the picker is skipped entirely. The wizard starts at ticket selection like a normal event.
Hidden paths
Toggling Visible off keeps the path off the public picker. The path's direct URL still works for anyone you share it with, which is the point — invitation-only audiences like Sponsors or Press get a private path with comp tickets, and you share the URL by email instead of listing it publicly.
If you need stronger gating than "unlisted", use access codes (a separate feature on the Access codes tab) so the registration is also rate-limited or pre-approved.
What paths don't (yet) do
Paths today gate ticket-type visibility per audience. They don't yet gate which price tiers inside a ticket appear, and they don't yet drive per-audience custom registration questions — those are both on the roadmap. If you need different questions for Speakers vs Attendees today, the workaround is to use Speakers-only ticket types and rely on the per-ticket question set.