Selling event tickets

Events can collect paid tickets, free registrations or RSVP choices. The event and its ticket types work together: the event supplies the date, venue and registration rules, while each ticket supplies the option a person selects.

Set up the event

1. Open Admin → Events and create the event.
2. Add the date, location, optional capacity and registration window.
3. Choose how it sells: Tickets, Entries, RSVP, or Auto when the event type should choose the default presentation.
4. Switch on admin approval only when every new registration should wait for a decision.
5. Save, then add at least one active ticket type or RSVP option.

Ticket types can be free or paid and can carry member-only access, early-bird pricing, sales start and end times, and a maximum number of seats per order. Use one ticket per real option or timed distance; do not use one generic ticket when later operations need to distinguish the entrants.

Capacity, approvals and waitlists

These controls differ by registration path:

• The event-level capacity is used by the RSVP option and summary. Ordinary ticket checkout enforces capacity on the ticket type itself. The current web ticket editor does not expose that per-ticket capacity, so do not assume the event capacity alone stops every ticket sale.
• Require admin approval applies to free registrations. A paid registration that completes payment does not wait in that approval queue. Approval and rejection are deliberate admin actions, not automatic decisions.
• A capped group booking is either accepted together or waitlisted together. A paid waitlisted group is not charged until promotion, when the buyer is sent a payment link.

Review the attendee list before launch and during sales. Owners can manage pending, registered, waitlisted, cancelled and attended records where those states apply.

Publish and test

Preview the public event page, complete one registration with the same ticket and payment route a guest will use, and confirm the ticket email and attendee record. A paid event needs a working PayStack connection for hosted online checkout.

At the door, the scan page validates ticket codes and records attendance. A second scan is flagged instead of silently admitting the same ticket twice. Staff can also record an appropriate cash or card door sale against a real registration.