Access control and door codes

An access control integration opens your doors for the people who booked, for the time they booked. Nobody has to hand out keys or stay at the desk for a late booking. Thril sends each booking to your lock system, and the customer gets a code, a door link or a door button on the booking.

Thril works with Thrilock, its own system, and with nine partner lock systems. Thrilight and QT Systems also switch lights on and off around bookings.

---

Common setupsCopy Anchor Link

Unstaffed evenings and early mornings. Map each court, studio or simulator room to the door that leads to it. A customer who books 21:00 gets a code that works from a few minutes before the start until a few minutes after the end. You set those margins with Access before the reservation and Access after the reservation.

A members' door on a schedule. With Thrilock, Rollock, Tolotrack or Kulku.io, a membership gives each member their own access during set hours, such as a gym open to members from 6 to 22. See Door access for members.

A door that stays open for an event. With QT Systems, the door is a resource of its own, and you book it for the hours it stays open. See QT Systems.

---

Access for bookings, classes and eventsCopy Anchor Link

Every booking on a resource mapped to the lock system gets access, whoever made it. A class or an event on the resource gives its confirmed participants the access of its booking. A booking waiting for payment gets access once it is confirmed. Blockers open no doors.

Each resource opens the door, lock group or access level chosen in its settings.

---

Comparing the systemsCopy Anchor Link

With QT Systems and Rollock, Use one shared access code per recurring series gives every booking in a recurring series the same code. The customer remembers one code for the whole season.

The door button works on the web and in the Thril app. Maximum distance from the venue limits it to customers near the venue, using the venue's coordinates and the phone's location. With Thrilock, staff can open any door from the Door remote in the dashboard. See Opening a door now.

---

Connecting a partner systemCopy Anchor Link

Each partner page lists what you need from the partner. Doors, readers, lock groups and access levels are set up in the partner's system. The steps in Thril are the same for every partner.

1. Open the system under Settings → System → Integrations and enter the details the partner gave you.
2. Set Access before the reservation and Access after the reservation (Door access before the reservation and Door access after the reservation in QT Systems).
3. Switch Status to Active and save.
4. In each resource's settings, choose the door, lock group or access level the resource opens.
5. Run Sync future reservations (Update future reservations for Kulku.io) once. Bookings made before you connected then get access too.

If your locks take bookings from another booking system today, agree with the lock supplier when Thril takes over before you run the sync.

---

Delivering the codeCopy Anchor Link

Thril sends each booking to the lock system one week before it starts, and a booking made later goes at once. The Code ready column in Comparing the systems shows which systems make the code at booking and which a week before.

The customer finds the code on the booking on the web and in the app, and in an email. Each partner page says how its code arrives. Customers can read where to find it in Getting into the venue.

---

When a customer's code does not workCopy Anchor Link

Open the booking and its Integrations tab. It shows the code the lock system holds for the booking, and its Status. Service bookings, classes and events have the same tab.

• Created or Updated: the lock system has the code. Read it to the customer. If the code does not open the door, check the door, lock group or access level in the resource's settings. If those are right, your lock supplier fixes the door.
• Pending creation: the code arrives a week before the booking. If the booking starts within a week, let the customer in and send the booking to Thril support.
• Pending confirmation: the code comes once the booking is paid or confirmed.
• Failed creation, Failed update or External failure: the customer sees your Fallback instructions on the booking. Let them in and send the booking to Thril support.
• Missing integration config: switch the integration on or choose the resource's door, lock group or access level, then send the booking to Thril support.

With Thrilock, follow When a door does not open. For a member who comes in without a booking, see When a member cannot get in.

---

Fallback instructionsCopy Anchor Link

Fallback instructions are your message to customers whose access Thril could not create, such as "If your code does not work, call 040 123 4567". Always show fallback instructions shows it on every booking, for example during a known outage. A resource can add its own instructions to the venue's.

When you switch an integration back to Active after a break, run Sync future reservations to give access to the bookings made in between.