A physical key passed to a guest, cleaner, or contractor is hard to track once it leaves your hand. A temporary access code stays under your control: you set the window it works in and the lock it opens, and you get a record each time someone uses it. This guide covers how time-limited and one-time codes behave, when to pick each type, and how to create, schedule, and revoke them.
How a temporary code behaves
A temporary code is a numeric (or alphanumeric) credential that the lock's controller accepts only under conditions you set. The lock stores the code and its rules locally, so the door still opens on schedule even if the gateway or internet is down. When a guest enters the code, the lock validates it, records the event, and — for one-time codes — marks it as used.
Three rule types cover almost every scenario:
- Time-limited (period) codes — valid from a start date/time to an end date/time. Ideal for a guest staying Friday 3 PM to Sunday 11 AM.
- One-time codes — valid for a single unlock, then auto-expire. Good for deliveries or a contractor who should enter exactly once.
- Recurring (cyclic) codes — valid on specific days or in specific windows, e.g. every Tuesday 09:00–12:00 for a weekly cleaner.
| Scenario | Best code type | Typical window |
|---|---|---|
| Hotel / short-term-rental guest | Time-limited | Check-in to check-out |
| Cleaner, weekly | Recurring | Fixed weekday window |
| Package delivery | One-time | Single use |
| Contractor, single visit | One-time | Single use |
| Staff with shifts | Recurring | Shift hours |
Creating a time-limited code
These steps assume your lock is already paired with the app and, for remote management, connected through a gateway. If you are still at the install stage, the smart lock installation and configuration guide covers that part.
- Open the lock in the app. Select the property and the specific door from the device list.
- Choose Send e-key or Add passcode. Open the access management menu and pick passcode rather than an app e-key.
- Select the code type. Choose Period (time-limited) and enter the start and end time. Use the guest's check-in and check-out times, with a buffer so an early arrival or late checkout still works.
- Generate or set the code. Let the app generate a random code (recommended — avoids predictable patterns like 1234), or set one manually for staff who need to memorize it.
- Assign an owner name. Label the code with the guest's or contractor's name. This is what appears in the audit trail.
- Send or share. Deliver the code by SMS, email, or the booking platform. Avoid sending it inside a shared group chat where others can see it.
- Confirm in the log. After the first use, open the lock's activity record to confirm the code opened the door and the timestamp matches expectations.
One-time vs recurring: picking the right one
A common mistake is using a period code for a cleaner who comes "some time during the week." That leaves the code valid 24/7 for the whole period. For staff who work predictable hours, a recurring code is safer: it is usable only on the days and hours you define, so a stolen code is worthless outside that window.
For deliveries or one-off contractor visits, a one-time code is best. After one successful unlock, the code stops working. If the delivery is rescheduled, generate a fresh one — never extend a one-time code into a period code "just in case."
Revoking a code
You should rarely need to revoke a time-limited code — expiry does the work for you. But when a guest extends a stay or a code is compromised, fast revocation matters.
- Open the lock's passcode list.
- Find the code by its owner name.
- Tap the code and choose Delete (or set the end time to now).
- The lock updates immediately over the gateway; for a lock without a gateway, the change applies on the next app-to-lock sync via Bluetooth.
On every turnover it is worth running through the same short list: old guest code expired or deleted before the new guest arrives; new code labeled with the guest's name; start and end times matching the booking with a buffer; first entry confirmed in the activity log; cleaners on recurring codes rather than period codes; and no code reused between guests. None of it takes long once it is routine, and it is what keeps the audit trail clean.
Habits that keep access clean
- One code per person. Sharing a single "guest" code across multiple bookings destroys your audit trail. If two guests used the same code and something goes wrong, the log can't tell them apart.
- Random over memorable. Predictable codes (birthdays, 0000, 1234) are the first thing an attacker tries. Let the app generate codes.
- Review the audit log weekly. A quick scan of entry times catches anomalies — a 2 AM unlock by a cleaner's code is a red flag.
- Expire, don't delete-then-recreate. For a guest extending by a day, edit the end time rather than issuing a new code; fewer active codes means less confusion.
- Keep a gateway online for instant revocation. A gateway lets you revoke remotely the moment you learn a code leaked. For properties without one, plan revocation around when someone can stand next to the lock with the app.
For how this scales beyond metal keys, keyless entry benefits for property managers goes deeper. The locks and gateways these codes run on are on the smart lock product page.
Temporary codes give you access that is time-boxed, attributable to one person, and expires on its own — which is what guest stays and contractor visits call for. Default to one-time codes for single visits, recurring codes for staff with set hours, and period codes for short-term-rental stays, and let the audit log do most of the oversight.