Participant Guide¶

Overview¶

The participant experience spans Discover browsing, RSVP or registration, ticket wallet, program agenda, session registration, networking, and post-event feedback—depending on which modules the organizer enabled.

Purpose¶

Help attendees navigate Nigall confidently from first click through event day.

Who should use it¶

Conference attendees
Wedding/community guests (RSVP)
VIP guests with special registrations
Returning users with multiple events

Benefits¶

Unified attendee dashboard at /attendees/
QR tickets for fast entry
Optional networking and session tools
Privacy self-service

Action	Path
Discover	`/events/discover/`
Event page	`/events/<pk>/<tag>/`
RSVP	`/events/<pk>/<tag>/rsvp/`
Register	`/attendees/register/<pk>/<tag>/`
Dashboard	`/attendees/`
Profile	`/attendees/profile/`
Ticket	`/attendees/registrations/<pk>/ticket/`
My agenda	`/program/events/<pk>/<tag>/agenda/`
Networking hub	`/attendees/registrations/<pk>/networking/`
Privacy	`/attendees/privacy/`

Prerequisites¶

Account recommended (required for most registration events)
Event link or Discover visibility
Payment method for paid tiers

Step-by-step — Full participant journey¶

Find event — Discover or direct link.
Register — RSVP sidebar OR attendee registration flow.
Pay — If paid, complete Stripe checkout.
Ticket — Save QR from ticket page.
Program — Register for sessions; build agenda.
Networking — Opt in; set visibility.
Event day — Show QR; attend sessions.
After — Feedback links if sent by organizer.

[SCREENSHOT: Attendee dashboard]

Field descriptions¶

Key attendee-owned records:

Record	Purpose
AttendeeProfile	Global profile across events
AttendeeRegistration	Per-event registration + ticket
RSVP	Per-event RSVP (non-attendees module)
Session registrations	Program module
Networking settings	Visibility, meeting requests

Business rules¶

Rule	Detail
Module gating	Features appear only if organizer enabled
Ticket access	Confirmed registrations only
RSVP update	Logged-in users can resubmit
Guest token	Guest RSVP uses `access_token` link

Validation rules¶

Profile required fields per registration form
Session caps enforced

User permissions¶

Participants manage own profile, tickets, privacy — not other attendees' data.

Workflow¶

flowchart TD Find[Find event] --> Reg[RSVP or Register] Reg --> Ticket[Ticket/confirmation] Ticket --> Program[Sessions optional] Program --> EventDay[Check-in + attend]

Examples¶

Conference power user: Profile complete, 5 session registrations, networking public.

Wedding guest: Guest RSVP only, no account, meal survey answer.

Best practices¶

Complete profile before registration for faster checkout
Download ticket QR before arriving
Set networking visibility intentionally

Tips¶

Registration list: /attendees/register/
Session feedback after attendance
Order history: /payments/my-payments/

Common mistakes¶

Mistake	Result	Fix
Lost guest RSVP link	Can't update	Contact host for resend
Wrong email on account	Missing tickets	Update profile email

FAQs¶

RSVP vs Register?
RSVP = simple headcount; Register = Attendees module with tickets.

Troubleshooting¶

See Glossary & Troubleshooting.

Screenshot placeholders¶

[SCREENSHOT: Registration tier selection]
[SCREENSHOT: Program my agenda]
[SCREENSHOT: Networking directory card]

Administrator notes¶

N/A for participants.

Developer/API notes¶

Mobile: tickets list, discover, RSVP endpoints — see Mobile App.

See also: Check-In & QR Codes