Short-Term Rental Access Control Software: One System for Locks, Gates and Common Doors

Short-term rental access control software gives every reservation its own code on every door the guest needs: the unit lock, the building entrance, the parking gate and any shared doors. The code is created from the booking and stops working when the stay ends. On locks that take codes online, it also changes when the booking changes and is removed if the booking is cancelled. This guide is for property managers and hotels with 10 or more units who have outgrown one app per lock brand. It covers what the software has to do, how SuiteOp handles locks, gates and common doors, which lock brands it connects to, and a worked example for a 25-unit portfolio.

What does short-term rental access control software do?

Once you run more than a handful of units, access stops being about the lock and starts being about the system behind it. For a portfolio, the software has to do six things:

• A code on every door: the guest gets a code on each lock their stay needs, and only for the dates of that stay.
• A code lifecycle driven by the PMS: new bookings, date changes, extensions and cancellations reach the locks without anyone retyping a code.
• Access tied to verification: a guest whose verification is under review or declined does not get a working code.
• Staff and vendor access: cleaners and maintenance staff get their own codes for the properties they work in, and a contractor's one-off code expires on its own.
• An audit trail: you can see which code opened which lock, and whether it was a guest, a staff member or a backup code.
• Recovery when a code fails: a guest standing at a door at 11 PM gets a working code without waiting for someone to answer the phone.

This is a different question from which smart lock to buy. For lock-by-lock comparisons, see the best smart lock and guest verification software for vacation rentals. This page is about the access control layer that runs across all of them.

Locks, gates and common doors in one system

Unit doors

In SuiteOp, a property's access code type decides who manages its codes. Dynamic codes are created and managed by SuiteOp on the smart locks you assign. Fixed codes stay the same, which suits a lockbox or a manual key. Import shows a code that another system manages, read from your PMS (property access instructions).

With a property set to Dynamic and a lock assigned, SuiteOp generates a code for each new guest and pushes it to the lock. When SuiteOp first takes over a lock, it removes every existing code except the master code, so that nothing from your previous system conflicts. It then pushes reservation codes, user codes for your team and backup codes (setting up smart locks in SuiteOp).

Gates, building entrances and shared doors

Most portfolios have more than one door per stay. SuiteOp handles this in two directions:

• Several locks on one property: a unit can have a gate door, a building door and an apartment door assigned, so the guest's access covers every entry point.
• One lock across several properties: a common-area door, such as a lobby, pool gate or gym, can be assigned to every unit whose guests should use it.

Buildings also get their own instructions. Instructions set at the group level appear before each unit's instructions in the guest portal, and the building's check-in summary is the place for a building or gate code that guests need before the door code (building-level instructions). If your gate runs on a callbox rather than a smart lock, see how to automate short-term rental callbox and gate access.

A code lifecycle driven by your PMS

SuiteOp reads reservations from your PMS. On locks that take codes online, each step of the booking moves the code:

• Booking confirmed: a code is created for each lock assigned to the property and its building. SuiteOp schedules it on the hardware for the stay: most locks receive it a set time before check-in, and some receive it when the access window opens.
• Code window: the code is valid for the stay, plus any buffer you set at the organization or device level.
• Dates change: SuiteOp recalculates the window and updates the code on the lock. A paid late checkout keeps the guest's code working until the new checkout time.
• Cancelled: the reservation's codes are removed from the locks.
• Verification: while a guest's verification is under review or declined, SuiteOp does not create or deliver their code.

The guest sees the code in the guest portal, or in your PMS messages through a variable where your PMS offers one. Codes can also sit behind a check-in instruction timer, so they only show a set number of hours (0 to 48) before arrival (check-in instruction timer). To understand why this matters, read why you should stop giving door codes to unverified guests.

When a code fails

Shortly after check-in time, SuiteOp checks that each reservation code is active on its lock and retries the ones that are not. Each online-connected lock keeps a pool of unused backup codes, three by default. If a code still fails after check-in, SuiteOp offers the guest a working backup code. Guests can also tap "My code is not working" in the portal to swap it themselves. You only need to step in when self-service is not available, for example on an offline lock (automatic backup code replacement).

Staff, cleaners and vendor access

Team access follows the same rules as guest access:

• Access Only users: a cleaner or maintenance technician can get their own code without a SuiteOp login. Their code goes onto each lock that supports staff codes in the property groups you give them, and they receive it by email (assigning codes to users).
• Contractors: a one-off visit can use a shared backup code with a note and an expiry date. The code expires on its own (sharing with contractors).

For the workflow side of vendor visits, see how to automate smart lock vendor access for STRs and hotels.

An audit trail for every door

Each device in SuiteOp has a History tab that shows the events the lock reports, including which code opened it: a user code, a reservation code or a backup code (device FAQs). Devices alert you when they go offline or when a code push fails, and you can mute a device that has an unreliable connection.

Remote control is on your terms. On a compatible device with remote control turned on, staff can lock and unlock it from SuiteOp, and if you also make the device public, guests can tap to unlock it from the portal, but only during the hours of their stay (device settings).

Which lock brands does SuiteOp connect to?

SuiteOp is hardware agnostic: every compatible lock looks and works the same way in SuiteOp, so a portfolio with mixed hardware is managed in one place (device FAQs). Lock brands that connect to SuiteOp include:

• Yale and August
• Schlage and Kwikset
• Salto and Dormakaba
• RemoteLock
• igloohome and TT Lock
• Nuki, Lockly and Ultraloq
• Z-Wave locks through SmartThings

Wi-Fi and Z-Wave locks both work with SuiteOp. Z-Wave locks connect through SmartThings. See every connected brand on the integrations page and in SuiteOp Smart Devices.

A worked example: a 25-unit portfolio

Here is one portfolio from setup to a full week of stays. The portfolio is an example: 18 apartments in one building with a gated car park and a lobby door, plus 7 houses across town. Reservations come from Guesty. Every apartment and house has a smart lock, and the gate and lobby each have a smart lock too. All of them take codes online and accept codes set by SuiteOp.

1. Connect the accounts. Connect Guesty and each lock account. The locks appear in SuiteOp's device list.
2. Assign the doors. Each apartment and house gets its own lock. The gate and the lobby door are each assigned to all 18 apartments, so one gate lock serves every apartment guest.
3. Set the building up as a group. The building's instructions cover parking and the lobby, and appear before each apartment's own steps.
4. Turn on Dynamic codes. Each of the 25 properties is set to Dynamic, and SuiteOp starts managing the locks.
5. Add the team. The cleaning crew are Access Only users on the building's group and the houses' group. Each person's code goes onto those locks, and they never need a SuiteOp login.
6. A booking arrives. A guest books apartment 4B. SuiteOp creates their code for the apartment, lobby and gate locks.
7. Verification. The 4B guest passes Identity Check, so nothing holds their code back. Another guest's ID is flagged for manual review, and SuiteOp does not create or send that guest's code while your team checks the ID against the selfie.
8. Arrival. The code is scheduled on all three locks for the stay's access window. Shortly after check-in time, SuiteOp confirms it is active on each lock.
9. A code fails. On one house lock, a guest's code doesn't activate. SuiteOp offers that guest a backup code, and they're inside without a phone call.
10. The stay changes. A guest buys a late checkout. Their code stays valid until the new time on every door.
11. A cancellation. A guest cancels a future stay. Their codes are removed from all three locks.

In this example the team made one decision all week: reviewing a flagged ID. The device History tab shows which code opened which door if a question comes up later.

How to evaluate short-term rental access control software

Whichever system you look at, ask it to show you these on your own properties and PMS:

1. Can one lock be shared by many units, and can one unit have several locks?
2. When a booking's dates change, does the code change on every lock without anyone touching it?
3. Is a guest whose ID is under review kept from getting a working code?
4. What happens when a code fails at 11 PM, and does the guest need to call anyone?
5. Can cleaners have their own codes for the properties they work in, and can a contractor's code expire on its own?
6. Can you see which code opened which door?
7. Does it work across the lock brands you already own?

To see SuiteOp run access control on your own locks, gates and PMS, book a demo.