How access controls work in OpenCourt (overview)
How OpenCourt connects to your club's smart locks for per-booking door codes and in-app unlocking — and how to choose between Seam, RemoteLock, Rhombus, and UniFi Access.
Access controls connect your club's smart locks to OpenCourt so every booking gets its own door code automatically — and, on supported locks, so customers can unlock the door from the OpenCourt app. This page explains how it fits together; the linked guides cover each task.
Access controls live under Settings → Access Controls and are available to admins with access-control permission.
What you get
Automatic door codes. Map a lock to a space (your courts, bays, or fields) and every booking on it gets a code that works only for that booking's time window, then disappears. Nothing to hand out or revoke.
In-app unlock. When you enable it, customers can unlock a mapped door from the OpenCourt app during their booking.
NFC/BLE proximity keys. Clubs on a Salto KS access-control system can grant phone-based access — the customer holds their phone to the reader instead of typing anything.
A full activity trail. Every code, every unlock attempt, and every change is visible in your admin panel.
Everything OpenCourt creates is added alongside your lock's existing setup — your staff codes, fobs, and cards keep working, and OpenCourt only ever removes the codes it created.
Which provider do I connect?
You connect one provider, and they come in two kinds.
Multi-brand platforms — Seam and RemoteLock. Both sit in front of dozens of lock brands, so you connect by signing in to the account you already have with them. Between them they cover the consumer and light-commercial locks most clubs buy (August, Yale, Schlage, Kwikset, Lockly and more), and Seam additionally reaches professional access-control systems: Salto KS, Brivo, and Avigilon Alta (formerly Openpath). If you already have an account with either platform, use that one.
Single-system integrations — Rhombus and UniFi Access. Pick these when you already run that specific system at your venue: Ubiquiti gear on the wall (Dream Machine, UniFi Access hubs and readers) means UniFi Access; doors managed at console.rhombus.com means Rhombus.
A couple of details behind that table: Rhombus is unlock-only — it never issues door codes. RemoteLock and UniFi Access generate the code themselves rather than OpenCourt generating it. And on UniFi Access, in-app unlock only works on doors bound to a hub.
UniFi Access runs on your own console rather than a vendor cloud, so it needs one extra setup step — making the console reachable from the internet. See Connect UniFi Access to your club.
Before you buy a lock, check it works with OpenCourt. See Which locks work with OpenCourt, and send us the exact model — we'll confirm whether it does PIN door codes, in-app unlock, and NFC/BLE proximity keys. Build quality and installation are questions for the vendor or your installer, not us.
How a door code reaches the lock
You connect a provider and map each lock to a space.
A customer books that space.
OpenCourt creates a code for the booking and schedules it onto the lock.
The code activates for the booking window, then is removed.
Codes are time-limited: by default they become active 30 minutes before the reservation starts and expire 10 minutes after it ends (each lock's access rule can adjust this). Exactly when the code is loaded onto the hardware depends on your scheduling mode — see Access codes & scheduling.
Start here
Set up
Which locks work with OpenCourt — check a model before you buy: brands and systems, and what each one supports.
Connect a Seam lock — the most common setup.
Set who can unlock doors from the app — turn on in-app unlocking and set per-lock rules for who can unlock and when.
Salto KS mobile access — phone-based access on a Salto KS system.
Run it day-to-day
Door codes day-to-day — look up any booking's code, see what customers see, and what happens when bookings change.
Access codes & scheduling — code timing, and Just-in-Time vs Native scheduling for high-volume clubs.
When something's wrong
A customer can't get in — troubleshoot door access — the triage guide for the front desk.
Disconnect or switch your lock provider — what disconnecting does, and how to change systems safely.
Coming soon
Kisi access control — an integration we're building for clubs already running Kisi.
Thermostat control — heating and cooling that follows your bookings.
Home Assistant — bookings driving lights, HVAC and whatever else you automate.
Common questions
Is every door code unique?
Yes — every booking gets its own code, and it only works during that booking's window.
The thing to know is that a code belongs to the booking, not to one person:
A space reservation gets one code. Whoever booked it and everyone playing with them all see the same code.
An event or program gets one code for that session, which every registered participant sees.
That's deliberate: nobody gets stuck outside because they weren't the one who made the booking. By default a code works from 30 minutes before until 10 minutes after, following the window your club set on that lock — outside it, the code does nothing.
What happens if the internet goes down?
Codes that already reached the lock keep working — they're stored on the lock itself, so customers can still type them in. New codes can't reach the lock until it's back online, and in-app unlock needs the lock online. If outages are common at your facility, prefer Native scheduling (codes load ~72 hours ahead) — see Access codes & scheduling.
Do our existing keys, fobs, and staff codes keep working?
Yes. OpenCourt adds booking codes alongside whatever your lock system already has, and only ever removes the codes it created.
Can I see which codes were used, and when?
Yes. Every lock has its own activity feed, and the club-wide Unlock History logs each door event with the time, the lock, what happened, and the method.
What it ties back to depends on how they got in:
Someone typed a door code — you see the code and the booking or event it belongs to, like 1027 · Coach-Led Drill Sessions. Because that code is shared by everyone on the booking, it identifies the booking, not the individual.
Someone unlocked from the app — they were signed in, so this one is attributable. Your club's activity log records the attempt by name, successful or not.
The door was opened by hand from the inside, or re-locked on its timer — there's no code involved, so there's nothing to attribute.
Do customers need a separate app for the door?
No. Codes and in-app unlock live in the same OpenCourt app they book with. The one exception is NFC/BLE proximity keys (Salto KS), which must use your club's branded app.