Managing Schlage® Locks Across Multiple Properties

Account structure

Use a single owner account, on an email address that belongs to the business rather than to a person, with the password in a shared password manager. Cleaners and co-hosts should be invited as household members rather than given the owner credentials, so removing someone does not mean changing everything.

Resist the temptation to create one account per property. It multiplies sign-ins, splits your activity history, and makes handover between staff painful. [VERIFY: current household-member limits and permission levels in the Schlage app.]

Whatever you choose, write it down. The most common multi-property failure is an owner account tied to a former employee's email.

Naming that survives a small screen

• Lead with the property, not the door: '12 Elm — Front', not 'Front door (Elm)'. Lists truncate on the right.
• Keep the property identifier short and identical everywhere — lock name, router SSID, your calendar, your cleaning schedule.
• Never name two locks the same thing across properties. Voice assistants and automations will pick the wrong one.
• Include the door role when a property has several: 'Elm — Front', 'Elm — Rear', 'Elm — Garage'.

Network per property

Every Wi-Fi lock inherits the reliability of whatever router the property has. For a portfolio, standardise: the same router model, the same 2.4GHz IoT SSID name and password at every property, band steering off, a DHCP reservation for each lock, and an access point within range of the door.

Standardising the SSID sounds trivial and is the single biggest time-saver. Swapping a lock between properties, or re-enrolling after a reset, becomes a two-minute job instead of a site visit with credentials you have to look up.

Where a property has poor coverage at the door, a Thread-based model with a border router on site is more reliable than fighting Wi-Fi — and runs over a year on batteries instead of under three months.

The records you must keep outside the app

• Each lock's programming code, stored in the password manager against the property.
• The HomeKit setup code for any HomeKit-capable lock, photographed before installation.
• Serial numbers and purchase dates, for warranty claims.
• The permanent codes: owner, cleaner, maintenance — and who knows each one.
• Battery replacement dates per lock, so replacement is scheduled rather than reactive.

Operating rhythm

Run a monthly pass across the portfolio: check every lock reports online, check battery levels, delete expired codes before they crowd the slot limit, and confirm the cleaner's recurring schedule has not silently lapsed. Fifteen minutes a month prevents most emergency call-outs.

Keep a spare lock of the same model on the shelf once you pass three or four properties. A failed lock replaced the same day costs you nothing; one waiting on delivery costs you a booking.

When to move off the official app

If you are managing more than a handful of doors with rotating codes, the manual workload becomes the argument. Home Assistant with the Schlage cloud API integration (roughly 30-second state polling) gives you one dashboard across every property and scriptable code management, at the cost of running and maintaining a server.

That is a real trade, not an obvious upgrade. Below about five properties, discipline beats infrastructure.