myTickets¶
myTickets runs ticketed events — concerts, games, shows, banquets. You describe the event, define the ticket types you want to sell, and myTickets creates the matching myShop products so families can buy through your normal checkout. Every ticket carries a unique number and QR code, and volunteers scan them at the door with the mobile app.
Setting up an event¶
- Creating an event — event details, publishing, and deleting
- Ticket types and pricing — prices, quantities, sale windows and limits
Selling¶
- Selling tickets through myShop — creating the shop products and what buyers get
- Selling at the door — cards with Tap to Pay on iPhone or a borrowed Stripe card reader; tickets delivered by receipt QR code
- Ticket products — the myShop side of the same link
- When a buyer doesn't get their ticket email — the lookup page and resending
At the event¶
- Scanning tickets at the door — scanner permissions, the mobile app, test tickets
- Digital programs — an online program families open from the event page
Who can manage myTickets¶
Managing events requires myTickets Admin Access, and myTickets must be enabled for your organization. Without both, myTickets doesn't appear in the sidebar at all.
One exception: deleting an event requires general Admin Access, not myTickets Admin Access. Everything else on this page — creating events, ticket types, shop products, programs and scanner permissions — is myTickets Admin Access.
See Granting access for how to assign groups.
The public side¶
Two myTickets pages are public — anyone with the link can open them, signed in or not:
- The event list at
/mytickets/ - An individual event page at
/mytickets/event/<event-name>/
Only published events appear. Draft events are visible on those pages to administrators only, which is why an unpublished event can look fine from your side and 404 for everyone else.