Skip to content
Menu

Bring the work around people together.

The event. The people who come. The talent who make it happen. Connect registration, relationships, and the work in between, so your team can keep moving without starting over.

A good event starts with a clear plan.

Set up the event in draft, add admission types, then publish when you’re ready to issue guest tickets.

Event details
Keep the name, description, venue, and schedule together.
Local time
Choose a named timezone for event dates and arrival times.
Ready to publish
Valid dates and at least one active ticket type are required before admissions begin.
Follow the preparation guide

From the first guest on the list to the last arrival.

Your team prepares the event, gives each guest a ticket, and checks that ticket at the door. Here’s what getting started looks like, including the handoffs along the way.

  1. Prepare the event.

    Choose the organization, add the venue and schedule, and create admission types. Set capacities and registration options while your team gets the details ready.

    Use the preparation checklist

    Ready for the first ticket

    Publishing requires valid dates, a named timezone, and at least one active ticket type. Add a capacity when places are limited.

  2. Open the way in.

    Let attendees register for a published event, or issue tickets from your workspace. Free registration is built in; paid checkout uses your configured Stripe Connect account.

    See how ticket issuance works

    A guest record is the starting point

    The ticket reserves admission. Simply adding someone to your people list does not give them a place; valid and checked-in tickets count toward capacity.

  3. Put the pass in their hands.

    Share the ticket claim link through your usual channels. An eligible recipient can collect it in My tickets, while a printed pass or saved code gives the entrance team another way to find it.

    Follow the pass-sharing guide

    Send the pass, plus the plan

    Include the date, venue, and arrival instructions. Claim links belong with the intended recipient. Apple Wallet and Google Wallet passes are available when the wallet services are configured.

  4. Confirm their arrival.

    At the entrance, scan a ticket with a compatible mobile camera or enter its code. See whether admission is confirmed, already recorded, or needs attention before welcoming the guest in.

    Prepare the entrance team

    One ticket, one recorded arrival

    A successful check shows the guest’s name and records the arrival. A repeated code returns “Already checked in” without adding another admission.

Work out what your event needs.

Who sends the tickets? What does the entrance team need? A few practical answers before you choose your setup.

Can we choose how people register?

Yes. Choose whether to list a published event and open public registration, or issue tickets from the workspace. Set admission types and capacity for the event. Paid registration requires an eligible, configured Stripe Connect account.

How do forms connect to our people records?

Build and publish a form, then review its responses. Map supported profile fields and choose whether a response links to an existing person or creates a record. Custom answers stay with the submission. Your team reviews matches before changing CRM records.

Will guests need a Turnstile account?

Attendees need a verified Turnstile account with two-step verification to register online or collect a ticket into My tickets. Your team can also hand out a printed pass. Attendee accounts do not grant access to your organizer workspace.

What does an entrance station need?

An internet connection, a teammate with check-in permission, and the correct published event. Mobile camera scanning also needs a compatible browser, camera permission, and HTTPS. You can type a code or use a scanner that enters text. Admission checks require a live connection; offline check-in is not supported.

What if a guest loses a pass or cancels?

Find an issued ticket by the guest’s name, email, or code, then share its pass or code again. If the guest is no longer coming, cancel an unused ticket to release the place and prevent that code admitting entry. A ticket that has already been used cannot be cancelled through this workflow.

Can several local teams use Turnstile?

Yes. Each organization has its own people, events, and tickets. Workspace roles apply across the organization. Parent and child organizations can be connected, but a parent administrator does not automatically gain access to a child. Grant descendant access explicitly when a colleague needs to work across a branch.

Connect the work that matters to your team.

Tell us where the handoffs get difficult—from event registration to people records or talent bookings. We’ll work through the right starting point.

Talk to us