Glossary

A short translation table for the words TicketSquad uses everywhere else.

Squad

Everyone trying to get to the same event together. There are 30 of you trying to go to Glastonbury 2027? That's 30 Squad members.

Group (buying group)

The Squad's sale-day checkout team, sized for the maximum tickets per transaction. If the ticket seller allows 6 per purchase, a 30-person Squad plays best as 5 Groups of 6 - five real attempts at the queue instead of one. For known events, TicketSquad works the group size out for you from the seller's real limits.

Named event vs transferable event

The two ticket modes - a question about the tickets, not the event:

• A named event sells tickets tied to a person's details at purchase (the Glastonbury model). Passing one on is usually impossible or costs a fee, so the flow is data-first and groups-first - see Named events.
• A transferable event sells tickets anyone can use: whoever holds it gets in. The centre of gravity is the swap board - see Transferable events.

Known event vs custom event

A known event is an entry in the TicketSquad catalogue. Linking your event to one prefills dates, venue, the per-transaction ticket limit, timezone, recommended data fields, and the right ticket mode from checked ticket rules. A known event can be either ticket mode - known is about the catalogue, named is about the tickets. Don't see yours? There's a "Request that we add it" button in event creation.

A custom event is one you build yourself, with full control over every detail.

Roles

Roles shape what you see and do in an event:

• Event owner - there's exactly one per event. Can transfer ownership, rename, archive, or delete the event. Owners are coordinators too.
• Coordinator - organises the Squad: edits event details, sale dates, imagery, invite links, group size and data fields; creates and renames Groups; sends reminders; generates sale-day snapshots.
• Group admin - steers one Group: manages its roster (when the coordinator allows it) and generates its sale-day board.
• Member - coming along: submits their ticket-buyer details and sees their group's roster and readiness.
• Helper - not a role but a participation state: someone who isn't attending but joins to help buy or run admin. Helpers sit on the "helper bench" until an organiser docks them to a Group, aren't counted in readiness or capacity, and can report a sale-day success for the group they're helping.

Communities have their own pair: a community owner (exactly one; can transfer ownership, change the privacy setting, archive) and community admins who help run the roster and settings.

Tiers

• Squad Solo - the free tier, forever. Join unlimited Squads; own or coordinate one active (unarchived) event at a time - archive one and the slot frees up.
• Squad Crew - for coordinators running several events at once, plus the known-events calendar.
• Squad Pro - adds the ability to create communities (joining is free on every tier, and an existing community keeps running whatever happens to the subscription).
• Hype Squad - a granted thank-you tier for people helping TicketSquad get good: every Squad Pro feature, free.

Open and Closed

The two privacy modes for events and communities - who can see members' personal details. Covered properly in Privacy.