Community owners · Events & ticketing
Selling event tickets
Create an event, choose its registration model, add ticket types with their places, choose who can register, test checkout and manage registrations.
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. For a map of everything JollyBee does for an event, start with Running events: what JollyBee covers.
Set up the event
- Open Operations → Events & Experiences → Events and create the event.
- Add when it starts and ends, the location and, if you like, a capacity. Times are in your club's time zone, and the form says which.
- Choose how it sells: Tickets, Entries, RSVP, or Auto when the event type should choose the default presentation.
- Tick Require admin approval for registrations only when every new registration should wait for your decision.
- Save, then add at least one active ticket type or RSVP option.
- Under Who can register on the event's page, keep Anyone to let people register with their name, email and mobile and no account, or choose Only signed-in people.
Ticket types can be free or paid and can carry member-only access (Members-only), a member price, early-bird pricing, Sales open (optional) and Sales close (optional) times, Places (optional) and Max seats per order (optional). Ticket times are in your club's time zone too. Max seats per order is how many places one person can register in one go: leave it blank or 1 for one, or set it higher so someone can register a family or group. Every way in keeps it: your event page, the cart, a widget on your website and the app. Only a sale at the door can take more, up to 10. Use one ticket per real option or timed distance; do not use one generic ticket when later operations need to distinguish the entrants.
An event can count as a membership benefit, its own or its category's. A member whose plan lets them register early for that benefit can buy a ticket as many days before its sales open as their plan gives, when they are signed in. A ticket with no sales open time is on sale to everyone as soon as the event is published, so there is nothing to buy early, and a registration through a widget on your own website opens at the normal time. See How memberships, benefits and categories tie together.
Capacity, approvals and waitlists
How places, approval and the waitlist work:
- Places (optional) on each ticket type is what stops sales. When every place is taken, the ticket shows as sold out. Each ticket's row shows its places taken and anyone waiting, for example "12 of 60 places taken · 3 waiting". You can't set places below the number already taken.
- The event's own Capacity doesn't stop ticket sales. It is shown on your event page, and a widget on your website shows the event as sold out once that many places are taken across its tickets. On an RSVP event, Capacity is how many people can RSVP.
- With Require admin approval for registrations on, every new registration waits in the attendee list until you Approve or Reject it, and nothing is approved or rejected for you. On a paid event people pay in the cart, and their place then waits for your approval; Reject and refund ticket turns it down and refunds them. A widget on your website sends people to the event's page to register. When a place frees up, the first person on the waitlist moves into it and waits for your approval too, as Awaiting approval in the attendee list. They're emailed that a place has opened and that you'll review it, with nothing to pay yet. Approve sends their ticket, or for a paid place a link to pay, and holds the place for 24 hours while they pay. Reject frees the place for the next person waiting.
- Places registered together on one ticket are given together or waitlisted together. A waitlisted group is offered places one at a time as they free up, so part of it can get in while the rest waits. The cart keeps no waitlist, so it takes a group only when every place fits. Nobody waiting for a paid ticket is charged until a place is offered to them: the buyer is then emailed a link to pay for that place, and on an event you review, only once you approve it.
- When a place frees up, it is offered to the first person waiting. Raising a ticket's places offers nothing by itself: when places are free and people are waiting, the ticket's row shows a button such as Offer 1 freed place to the waitlist. It asks you first, then emails each person in the order they joined: their ticket for a free place, or a link to pay for a paid one. On an event you review, they move up to await your approval instead, and Approve sends the ticket or the link.
Review the attendee list before launch and during sales. Owners can manage pending, registered, waitlisted, cancelled and attended records where those states apply. See who's coming and check people in covers the headcount, the list and its download.
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. Try it signed out too: unless the event takes only signed-in people or the ticket is Members-only, a visitor registers in the cart with their name, email and mobile, pays the normal price and gets their ticket by email. A paid event needs a working PayStack connection. While PayStack is in Test, test payments go through and the door lets them in, marked as a test. Once it is Live, the door turns test tickets away, so cancel your test registrations before you go live. Share an event: link, QR code and sticker covers getting the word out.
At the door, Door scan → checks each ticket code and records attendance. A second scan is flagged instead of silently admitting the same ticket twice, and a ticket whose payment hasn't gone through is turned away. Staff can sell at the gate with Record sale, which takes up to 10 places, cash or card, and doesn't wait for approval.