
Central role and visitor management across sites, real-time joiners and leavers, portfolio reporting, consistent policy, and offline-capable doors as the fallback.
Cloud access control moves the access policy from a panel in a back room to a managed service: administrators define roles, visitors and schedules once, doors at every site enforce them, and a joiner or leaver is reflected across the portfolio from one change. It is the management layer that makes multi-site retail, coworking, gym and office chains operationally consistent, with reporting that compares sites rather than stitching spreadsheets. Cloud does not mean doors stop working when the internet does — well-designed devices hold local schedules and buffer events, the offline behaviour covered in the resilient-sites solution. The distinction that matters is between the central management plane and local enforcement, which are specified together. The multi-site solution covers rollout structure, the offline solution covers resilience, and the office solution covers a single tenancy.
| Central policy | Roles, visitors, schedules and permissions are defined once and applied to every authorized site |
| Real-time change | Joiners, leavers, lost credentials and contractor windows update across the portfolio from one action |
| Portfolio reporting | Access events and exceptions are compared across sites for compliance and operations |
| Local enforcement | Doors and controllers enforce locally and buffer events, so outages degrade safely rather than lock users out |
| Visitor lifecycle | Hosts pre-register guests who receive dated credentials at any included location |
| Admin roles | Global, regional and site administrators act within scoped permissions and an audit trail |
| BOM shape | Cloud-ready controllers and locks per site, local fallback design, enrollment and rollout scope |
Multi-site and fast-changing organizations choose cloud policy; single static sites with no remote-management need may remain on local panels.
| Dimension | On-premise panels per site | Cloud-managed policy |
|---|---|---|
| Joiner / leaver | Handled separately at each site | One change applies portfolio-wide |
| Reporting | Logs collected site by site | Cross-site comparison in one place |
| Consistency | Local rules drift apart over time | One policy version across locations |
| Outage | Depends on panel design | Local schedules continue with buffered events |
| Scaling | New site needs its own setup | New site enrolls into the existing policy |
| Typical fit | Single static facilities | Chains and multi-site organizations |
Every site still needs capable doors and controllers; the cloud layer changes how policy and changes reach them, not the physical access design.
| Opening | Typical door | Lock approach |
|---|---|---|
| Site entrance | Lobby or turnstile at each location | Cloud-enrolled reader enforcing the central policy locally |
| Floor / zone door | Interior readers across the site | Role groups applied consistently with other locations |
| Secured room | Server, cash or restricted door | Named groups inherited from central policy with local recording |
| Site controller | Local gateway between doors and cloud | Holds schedules and buffers events through outages |
| Visitor point | Reception or kiosk entry | Host-registered visits issued centrally and honored onsite |
| Service / MEP | Plant and receiving doors | Work-order windows managed in the central schedule |
This example illustrates a typical configuration, not a specific customer project. Site count, door mix and admin model drive the list.
| Component | Typical logic | Notes |
|---|---|---|
| Cloud-ready doors | Enrolled readers and locks per site | Capable of local enforcement and event buffering |
| Local controllers | Gateways providing offline resilience | Sized per site door count and network conditions |
| Policy enrollment | Roles, zones and visitors mapped at rollout | Global, regional and site admin scopes defined |
| Fallback design | Behaviour during outages and reconnect | Documented with reconciliation expectations |
| Rollout spares | Standardized hardware held regionally | Swap by named site staff under the current MOQ policy |
The practical change is where policy lives and how fast it moves: an administrator adds a joiner to role groups, removes a leaver, extends a contractor or pre-registers a visitor once, and the change reaches every authorized site without calling local staff or visiting a panel. Reporting becomes cross-site, so a regional manager can compare after-hours exceptions across locations rather than collecting logs by email. Local doors still enforce access physically; the cloud is the management and reporting plane, which is why door and controller quality remains as important as in any system. Organizations value it most where staff, members or stores rotate between locations and policy drift between sites has caused inconsistent security.
A properly specified cloud deployment keeps local controllers and doors enforcing the last synchronized schedule and buffering events, so staff and visitors with valid credentials continue to enter and records reconcile when the link returns; the doors do not wait on a cloud response for every opening. Actions that genuinely need the central service, such as issuing a brand-new credential, follow a documented local fallback until reconnection. The maximum offline behaviour and sync expectations are set per site, and sites with poor connectivity use controllers matched to that reality. The pilot site includes a deliberate outage precisely so the organization experiences graceful degradation rather than assuming it from marketing material.
Administration itself follows scoped roles: a global administrator defines policy, a regional manager acts within their locations, and a site manager handles only local visitors and staff, with every administrative action recorded. This prevents a compromised or over-broad account from changing the entire estate and matches responsibility to actual authority. Sensitive changes can require approval or break-glass procedures, and service-account access is separated from human logins. The role model is designed before enrollment begins, because retrofitting admin scopes onto live sites invites either lockouts or excessive permissions. Onboarding and leaver processes for administrators themselves follow the same discipline.
Yes, when the deployment can show where data resides, how access events are retained and exported, how administrators are authenticated, and how local enforcement behaves offline — the same evidence questions a regulated buyer asks of any system, directed at the service and the devices. Government, finance and healthcare buyers document these points and run a pilot before committing portfolio-wide, and some impose data-residency or retention requirements that must be confirmed in writing rather than assumed. The devices and controllers remain within the physical and standards requirements of the building. The data centers guide covers the audit mindset these buyers apply at the doors.
The BOM covers cloud-capable readers and locks at each site, local controllers sized for door count and connectivity, policy enrollment, admin setup and regional spares, with MOQ and lead time confirmed in writing per quotation. Organizations pilot one site through joiners, visitors, an outage and cross-site reporting before enrolling the network in waves. Send the site count, per-site door lists, admin-role structure and connectivity notes, and the quote maps each line to enrolled hardware and rollout rather than a single licence figure.
Send the site count, per-site door lists and admin-role structure — receive an enrollment-mapped 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