Core concepts.

Eight objects carry the whole platform. Learn what each one owns and the rest of the documentation reads easily.

Team

A team is the account everything else belongs to. Your events, your venues, your guest lists, your saved question sets: all of it is owned by a team, not by you personally.

Signing up creates a team for you. You can belong to several, and the team selector at the top of the sidebar decides which one you are looking at. Switching teams switches every list on every page.

A team can also publish a team website at /o/your-team, listing its published events in one place. Build it from Team Website in the sidebar.

People inside a team hold one of three roles. An Administrator can do almost anything, including changing what other people can do and managing billing. Only the team owner can transfer or delete the team. An Editor can create and change events, tickets and guests, and edit the team's name, logo and team website, but cannot manage members or billing. A Member can look but not touch: useful for a client, a sponsor, or a volunteer who only needs the numbers.

Event

An event is one thing that happens: a race, a conference, a show, a monthly meetup. It holds the name and description people read, the schedules, the ticket tiers, the guest list, the terminals, and the public web page.

An event carries a status. Draft means you are still building it, Published means it is out in the world, and Completed or Cancelled mean it is over. Status changes what the Overview page shows you, and closed events freeze their guest records so history stays accurate.

Schedule

A schedule is a session people check in to. That is the important part: check-in happens against a schedule, never against the event as a whole.

A one-day event has one schedule. A conference with a workshop day and a main day has two. A race with kit collection the night before has two, and a runner who collects a kit and then runs has two separate attendance records, one for each.

Each schedule has its own location, its own start and end, its own publish switch, and its own check-in switch. Turning check-in off for a schedule stops the scanner accepting tickets for it without touching anything else.

Ticket tier

A ticket tier is what a guest holds. Every guest has exactly one.

A tier carries a name, an optional description, a price in your team's billing currency, and an optional stock limit. It also decides which schedules it admits the holder to: all of them, or a chosen few. A Day 2 Only tier is just a tier bound to the day two schedule.

Setting a price of zero makes the tier free. Leaving stock empty makes it unlimited. Turning a tier inactive hides it from the public page without deleting anyone who already holds one.

A tier can also carry a fieldset, which is how you ask VIPs a question you do not ask everyone else.

Fieldset

A fieldset is a reusable set of registration questions: dietary requirements, shirt size, company name, emergency contact. You build it once under Fieldsets in the main sidebar, then attach it to as many ticket tiers, across as many events, as you like.

Each question has a type, from plain text through single and multi select to dates and yes/no. The answers land on the guest record and travel with the guest into your exports.

Guest

A guest is one person coming to your event, holding one ticket tier, carrying one QR code.

Guests arrive three ways: they register on your public page, you import them from a spreadsheet, or you add them by hand at the desk. However they got there, they end up in the same list with the same fields.

A guest record holds the attendee's name and email, the billing contact who paid (often the same person, not always), the ticket tier, the answers to any fieldset questions, and every attendance record they have collected.

Order

An order is one registration's money. It holds the lines that were bought, every payment taken against it and every refund made, and the state the whole thing is in. A free registration has an order too, worth nothing.

The order is what the buyer sees on their own status page, where they can send proof of payment for an offline transfer, and what you see under Orders on the event. It is the record you go to when someone asks what they paid.

Terminal

A terminal is a named place people check in: a door, a gate, a lane, a desk. It is not a device. Five volunteers with five phones can all work Main Door, and their scans all record against Main Door.

Every attendance record stores which terminal it came through, which is what makes the live door feed and the terminal leaderboard useful during an event and what makes an incident traceable afterwards.

How they fit together

Everything else in this documentation is a detail hanging off one of those eight.