Getting Started

Run your first event.

From an empty account to a working QR ticket in fifteen minutes.

This walkthrough takes an empty account to a published event with a working QR ticket. It assumes nothing except an email address, and it takes about fifteen minutes at a normal pace.

Before you start

You need one thing: an account. Signing up creates a team for you automatically, and everything you make from then on belongs to that team. If someone has already invited you to their team, accept the invitation first so your work lands in the right place.

You do not need a payment gateway, a card, or any hardware. Free events cost nothing to run, and the scanner works on the phone already in your pocket.

Step 1. Create the event

Open Events in the sidebar and choose Create Event.

The events list, with the create button in the top right
Every event your team runs lives here, newest first.

An event needs a name to exist. Everything else can wait.

The create event form, showing the name field and the template picker
Templates pre-fill the schedule and ticket tiers for a common shape of event.

Under the name you can pick a template. Blank gives you an event with nothing in it, which is the right choice if your event does not look like anything on the list. The templates cover the shapes that come up most: an athletic event, a single or multi day conference, a recurring meeting. A template only sets up starting tiers and schedules for you, and you can rename or delete every one of them afterwards.

Choose Create Event and you land in the event workspace.

Step 2. Learn the workspace

You land on the event Overview, and the sidebar beside it is the whole event. It is grouped by what you are doing:

  • Setup holds Basics, Schedules, Tickets, Guests, Event Website and Terminals. This is the build.
  • Operations holds Scanner, Inspector, Attendance, Observer and a link to your public page. These are the event-day tools, and they open in their own tabs.
  • Configure holds Settings, where registration is opened and closed.
  • Tools holds Exports.

While the event is still being built, the Overview is a setup checklist. It is the page telling you what is left to do, rather than charts of activity that has not happened yet.

The event overview of a new event, showing the setup checklist
On a new event the Overview is a checklist. Finished steps are ticked and struck through, and the next one is highlighted.

The checklist tracks six things, in the order the Setup group lists them:

  1. Basics. A name and a description, so guests know what they are registering for.
  2. A schedule. When and where the event happens. One is enough to start.
  3. A ticket tier. At least one, even for a free event. Every guest holds a tier.
  4. Guests. Imported by you, or registered by themselves once you share the page. This one is optional, and the checklist marks it as such.
  5. A terminal. The named door or desk that check-ins get recorded against.
  6. The event website. A banner and a tidy public page.

Some of these are already ticked the moment you create an event, because a new event arrives with a starting ticket tier and a terminal. Every row is a link, so you can work the list from the top without hunting through the sidebar.

Once the five required steps are done, the Overview stops being a checklist and becomes the charts you will watch on the day.

The event overview page
After setup, the same page carries the charts. The sidebar beside it is the whole event.

The next four steps work down that list.

Step 3. Add a schedule and a ticket tier

A schedule is a session people check in to. A single-day event has one. A conference with a workshop day and a main day has two. Give it a name, a location, a start and end date, and start and end times.

A ticket tier is what a guest holds. It carries a price, an optional capacity limit, and the schedules it admits you to. Set the price to 0 for a free tier. Leave stock empty and the tier sells until you stop it.

If you created your event from a template, both of these already exist. Open them, rename them, and change the dates.

Step 4. Add a terminal

Open Terminals and add one. Call it what the people working it will call it: Main Door, Gate B, Registration Desk. Every scan records which terminal it came through, so at the end of the night you can see which door was busiest and where a problem scan happened.

Step 5. Get a ticket into your own hands

You do not need a real guest to test this. Open Guests, choose Add Guest, and put yourself on the list with your own email address and any active ticket tier.

From the guest's row menu, choose Send PDF. Check your inbox. You now have a real QR ticket, generated the same way every attendee's will be.

Step 6. Scan it

Open Scanner from the Operations group in the event sidebar. It opens in its own tab, because at the door you want it and nothing else on the screen.

Pick your terminal and your schedule, allow the camera when the browser asks, and point the phone at the QR code on your screen or on paper.

The scanner, lined up on a guest ticket
Any phone with a camera works. There is no app to install.

A green result means the guest is in and an attendance record now exists against that terminal and that schedule. Scan the same code again and you get told they are already checked in, which is exactly what you want a second scan to do.

What to do next

You have a working event. From here:

Last reviewed August 22, 2026