
Turnover and vendor credentials across scattered units, consistent resident and staff policy, remote changes and audit visibility for managers of many properties.
Property managers running scattered rentals, mixed commercial units or a regional portfolio face an access problem defined by distance: doors spread across cities, turnover every few days, vendors who need one-hour windows, and owners who want to know the building is controlled without a site visit. Centralized property access applies one credential policy to the whole portfolio — a new tenancy activates doors from the lease, a cleaner receives a turnover window, a plumber gets a dated code, and move-out withdraws everything centrally, regardless of lock brand mix where supported. Managers gain portfolio-wide visibility of events and expiring access instead of phoning each local caretaker. The property management guide covers the operating model, the landlords page covers single-door starts, and the multi-site solution covers the management architecture.
| Portfolio policy | Turnover, vendor and staff rules are defined once and applied consistently across every property |
| Lease-linked doors | Tenant credentials activate and lapse with tenancies, including across mixed lock hardware |
| Vendor windows | Cleaners, trades and inspectors receive dated door-and-time codes issued centrally per job |
| Remote changes | Lockouts, extensions and revocations are handled without driving to the unit |
| Owner visibility | Owners and managers see access events and outstanding credentials per property |
| Local fallback | Each site keeps a documented offline and emergency path for connectivity or device failure |
| BOM shape | Per-entrance hardware across properties, shared management layer and portfolio spares |
Portfolios beyond a small local set centralize policy and issuing; a handful of nearby doors may keep a local caretaker with standardized rules.
| Dimension | Local keys and caretakers | Centralized credential policy |
|---|---|---|
| Turnover | Caretaker rekeys or recodes on site | Doors updated remotely against the lease |
| Vendors | Keys collected and returned in person | Dated windows issued and withdrawn per job |
| Lockouts | Staff dispatched to the door | Verified and resolved remotely with a fallback |
| Oversight | Status known only by phoning site staff | Portfolio-wide events and expiring access visible |
| Hardware mix | Every building different and unmanaged | Standardized policy across supported hardware |
| Typical fit | Small local portfolios | Regional and scattered rental managers |
Unit entrances carry tenant credentials; common, vendor and staff doors are where the centralized policy saves the most travel and risk.
| Opening | Typical door | Lock approach |
|---|---|---|
| Rental unit | Scattered apartment or house doors | Lease-linked credentials managed regardless of location |
| Common entrance | Lobby or street door in multi-unit blocks | Coordinated with building rules and the tenant credential |
| Vendor access | Any door needing trades or cleaning | Dated job-scoped windows issued centrally |
| Commercial unit | Shop or office within the portfolio | Tenant-managed inner doors under a portfolio outer policy |
| Storage / utility | Shared bin, bike or plant rooms | Service windows isolated from tenant credentials |
| Owner / manager | Manager office or mobile management | Portfolio dashboard with per-property event visibility |
This example illustrates a typical configuration, not a specific customer project. Property count, door mix and turnover volume drive the list.
| Component | Typical logic | Notes |
|---|---|---|
| Entrance hardware | Standardized supported locks per property door | Selected for remote updates and offline behaviour |
| Common-door scope | Lobby and shared doors where buildings permit | Coordinated in writing with strata or landlords |
| Vendor management | Central issuing of dated job windows | Cleaner and trade codes withdrawn automatically |
| Management layer | Portfolio policy, dashboard and event records | Role separation between managers, owners and staff |
| Portfolio spares | Locks and batteries held regionally | Serviced to turnover cycles under the current MOQ policy |
The lease record drives the doors: when a tenancy starts, the unit and any permitted common-door credentials are activated centrally, and at move-out they are withdrawn on schedule so the next tenancy starts clean without anyone visiting to rekey. Cleaners and inspectors receive turnover windows between tenancies, and vendors receive dated codes for the job, all issued from the same management layer regardless of which city the door is in. Local caretakers remain in the workflow for physical tasks and emergencies but no longer hold the only path to access. The pilot cluster deliberately spans more than one area to prove that distance no longer changes the process, including a same-day turnover between two bookings.
Centralization works best on a standardized, supported hardware set, because remote credential changes, offline behaviour and event recording depend on the lock’s capabilities; mixing many unrelated consumer locks creates gaps where some doors still need physical visits. Portfolios typically standardize new installations on one supported range and migrate existing doors at natural replacement points, while a documented inventory shows which doors remain on legacy handling. The management layer separates manager, owner and staff roles so an owner can see their building without controlling other properties. This hardware standardization is specified during the portfolio audit rather than discovered during an emergency lockout.
A verified lockout is resolved through the management path — identity confirmation against the tenancy, then a credential extension or one-time code — with the event recorded, rather than dispatching staff or sharing a permanent code. Hardware failures and doors the system cannot reach fall back to a documented local path and emergency keyholder, and free egress is always preserved. Verification rules are decided in advance so a late-night call does not rely on whoever answers improvising. Managers monitor low batteries between tenancies to service them at turnover. The pilot cluster rehearses a nighttime lockout at a property with no onsite staff to validate the full response.
Owners can be granted read visibility into their own building — door events, active credentials and expiring vendor windows — without gaining control over other properties or the manager’s settings, which keeps multi-owner portfolios clean and confidential. Managers use the same records to prove access was withdrawn at move-out and to review vendor punctuality. Reports are defined around what each owner actually wants, usually turnover confirmation and exception events rather than a constant feed. Separating owner visibility from manager control is part of the role design before onboarding, since retrofitting permissions across a live portfolio is harder.
The BOM inventories every entrance across the portfolio, adds permitted common-door controls, the shared management layer, regional spares and battery servicing, with MOQ and lead time confirmed in writing per quotation. Managers pilot a cross-city cluster through turnover, a vendor job and a lockout before onboarding the rest. Send the property count, entrance inventory, monthly turnover volume and existing lock types, and the quote maps each line to standardized door hardware and the management rollout rather than per-building guesses.
Send the property count, entrance inventory and turnover volume — receive a portfolio-standard BOM with written MOQ and lead-time terms.
Discuss your project (RFQ)Project configurationsLast updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team