
Shared role and visitor policy across branches, enrollment of new sites onto a standard, regional and site-level administration, and comparable reporting.
Growing from one secured site to a network changes the access problem: every new branch otherwise invents its own codes, keeps its own leaver list and reports in a different format, which is how regional managers lose track of who can open what. Multi-site access management establishes one policy standard — roles, visitor handling, contractor windows, keyholder rules — applied consistently, while each location keeps genuinely local settings such as opening hours, emergency contacts and site-specific doors. New stores, clubs, clinics or offices enroll onto the standard instead of starting from scratch, and reporting compares sites on the same definitions. The cloud solution covers the technology plane, the centralized property solution covers scattered rentals, and the retail solution covers chain stores.
| Shared standard | Role definitions, visitor rules and keyholder policy are identical across enrolled sites |
| Local settings | Opening hours, emergency contacts and site-specific doors stay managed per location |
| Site enrollment | New branches onboard a standard template with a pilot rather than bespoke setup |
| Regional roles | Area and regional managers act across assigned sites with scoped permissions |
| Comparable reporting | After-hours, exceptions and credential hygiene use one definition across the network |
| Traveling staff | Staff who legitimately move between branches carry credentials scoped to their schedule |
| BOM shape | Standard hardware per site format, enrollment scope, regional spares and training plan |
Networks beyond a few sites standardize policy and hardware; truly autonomous franchisees may keep local control under a brand guideline.
| Dimension | Independent systems per site | One multi-site standard |
|---|---|---|
| New branch | Bespoke setup and training each time | Enrolled onto a proven template with a pilot |
| Leavers | Each site removes access separately | One revocation across authorized locations |
| Reporting | Inconsistent formats and definitions | Comparable metrics network-wide |
| Local hours | N/A or rigid central schedule | Shared policy with per-site hours and doors |
| Franchise fit | Fully local, no brand view | Brand standard with local administration option |
| Typical fit | A few unrelated sites | Chains, branches and regional networks |
Each site keeps its own entrance, floor and back doors; the standard changes how policy and hardware are chosen and enrolled across them.
| Opening | Typical door | Lock approach |
|---|---|---|
| Site entrance | Branch main or staff entrance | Standard reader with local opening hours and keyholder rules |
| Customer / public door | Trading or reception threshold | Shared visitor policy adapted to local flow |
| Back of house | Stock, cash or treatment rooms | Standard role groups with site-specific door mapping |
| Regional office | Area manager access across sites | Scoped multi-site credentials with per-site records |
| New site shell | A branch awaiting enrollment | Standard hardware and policy template applied at fit-out |
| Service entry | Goods and maintenance doors | Common contractor-window policy with local vendors |
This example illustrates a typical configuration, not a specific customer project. Site formats, enrollment waves and franchise model drive the list.
| Component | Typical logic | Notes |
|---|---|---|
| Standard hardware | A supported lock and reader set per site format | Chosen for consistent rollout and maintenance |
| Policy template | Roles, visitors, keyholders and contractor rules | Applied at enrollment with local hour and door settings |
| Admin structure | Global, regional and site permission scopes | Defined before the first wave enrolls |
| Enrollment waves | Pilot then regional rollout with training | Scheduled to fit fit-outs and operating calendars |
| Regional spares | Standard parts held per region | Serviced by named staff under the current MOQ policy |
The standard fixes the things that must be comparable: role definitions, visitor and contractor handling, keyholder rules, naming conventions and reporting definitions, so a regional manager sees one version of the truth. Local settings cover the things that genuinely differ per branch — opening hours, site-specific doors and zones, emergency contacts, and local vendors — which remain administered within the standard by site managers. The boundary is written down before enrollment, because ambiguity between central and local control is the main source of friction in a rollout. The pilot branch deliberately exercises both a network-wide change and a purely local one to prove each path works as intended.
Instead of designing security from scratch, a new branch is fitted with the standard hardware set and mapped onto the policy template: its entrance and back doors are assigned to the standard role groups, its local hours and emergency contacts are entered, and a short pilot exercises keyholders, visitors and a contractor before the site is declared enrolled. Fit-out teams receive the hardware and wiring standard before construction, which reduces both cost and delay. The first few enrollments after the pilot are supported centrally, after which regional teams onboard sites themselves. This templating is where multi-site management delivers its biggest saving — the second hundred branches cost far less management attention than the first ten.
Regional and area managers hold credentials across exactly the sites in their remit, with administrative actions recorded per site, and head office roles stay separate from field roles so an account cannot unintentionally change every branch. Staff who legitimately travel — area trainers, auditors, relief managers — receive cross-site access bounded to the dates and locations of their schedule rather than a permanent all-sites pass. The same model applies to franchise networks, where the brand can hold reporting visibility while the franchisee administers staff locally. Permission scopes are reviewed when territories change so access does not accumulate.
Comparability comes from defining every metric once: what counts as an after-hours entry, how quickly a leaver must be disabled, what an active contractor credential is, and how door-forced or door-ajar events are categorized. With shared definitions, regional reporting shows genuine outliers — a branch with stale credentials or repeated forced-door events — rather than differences in how each site logged them. Reports are kept focused on exceptions and hygiene rather than flooding managers with raw events. The reporting catalog is agreed with operations before the first wave, and the pilot branch validates that its data maps correctly, since a mislabeled event type would corrupt every later comparison.
The BOM applies the standard hardware set to each site format, adds enrollment and training scope, the admin structure, regional spares and support paths, with MOQ and lead time confirmed in writing per quotation. Networks pilot one representative branch, enroll a first supported wave, and then scale regionally. Send the site count, site formats, current hardware and franchise structure, and the quote maps each line to standard hardware and enrollment waves rather than pricing every branch as a unique project.
Send the site count, site formats and franchise structure — receive an enrollment-wave 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