How to Manage Multiple Smart Locks From One App

A single lock at a single door is easy to manage from memory. Once a household, landlord, or business is responsible for a handful of locks across different doors or different addresses, the same tasks — issuing a code, checking a battery level, reviewing a log — take longer to find and are easier to get wrong, such as sending a guest code for the wrong property.

1. Give every lock a clear, specific name when it is added — the property address plus the door, such as "12 Oak St – Front Door", rather than a generic default name. This matters most once the list grows past three or four locks.
2. Group locks by property or site if the app supports it, so a single view shows every door at one address together rather than an undifferentiated list of every lock on the account.
3. Assign a per-door or per-property admin for larger portfolios, so one person manages a subset of locks rather than a single admin account being a bottleneck and a single point of failure.
4. Install one gateway per physical site, not per lock. A single gateway can usually relay commands to every TTLock-compatible lock within Bluetooth range at that address, so remote code issuance and log syncing work without a site visit.
5. Use bulk actions for repeated tasks, such as issuing the same cleaner a cyclic code across several properties at once, instead of repeating the same manual steps per lock.

A consistent naming convention pays off as the number of locks grows. Useful patterns include property + door ("Unit 4B – Main Entrance") or site + zone ("Warehouse – Loading Dock"). Whatever the pattern, apply it to every lock from the start rather than retrofitting names later.

• Decide who is a full admin versus a limited user for each lock or group. A property manager overseeing several buildings may need full admin rights everywhere, while an on-site caretaker only needs rights for their own building.
• Keep one super-admin account that has visibility over every lock, even if day-to-day management is delegated, so a single point of contact can always regain control.
• Separate guest, staff and admin credentials across every lock consistently, so the type of credential itself tells you something about who holds it, independent of which property it is on.

• One gateway does not cover multiple buildings.Bluetooth range is limited to roughly the size of a single building or a floor; a portfolio spread across addresses needs a gateway at each one.
• Bulk actions apply to whatever is selected. Double check the lock group before running a bulk code change, since applying it to the wrong group revokes or grants access unintentionally.
• Vague names cause mistakes under time pressure. A list of ten locks all named "Front Door" makes it easy to issue a code to the wrong property.
• Smart Lukko is an independent app. It works with TTLock-compatible locks from multiple manufacturers but is not affiliated with TTLock/Sciener, so hardware-specific limits (like gateway range or maximum stored users) vary by lock model.