| Cloud-Managed Deployment | Multi-site offices, hotels, student housing, healthcare facilities, and property portfolios requiring centralized administration. | Wi-Fi Bluetooth Web dashboard
Administrators issue, change, or revoke credentials remotely. | Centralized user management, real-time activity records, remote configuration, scheduled permissions, and easier administration across multiple locations. | Requires dependable network connectivity, suitable cybersecurity controls, account protection, and a defined data-retention policy. | Mechanical override key, authorized mobile credential, temporary PIN, or a site emergency procedure. Backup power may be needed when electronic access depends on building power. |
| Offline or Standalone Deployment | Small offices, storage rooms, utility areas, remote buildings, and locations with limited or unreliable internet access. | Local keypad RFID credential Bluetooth
Access decisions are made locally at the lock or through periodic local administration. | Continues operating without an internet connection, reduces network dependency, and can be practical for isolated doors or smaller installations. | Activity synchronization and remote revocation may be limited. Lost credentials require prompt local management, and battery condition must be monitored. | Physical key override, master credential, emergency PIN, or an approved maintenance access procedure, subject to the facility’s security policy. |
| Hybrid Deployment | Facilities that need centralized oversight for main entrances while keeping selected interior or remote doors locally controlled. | Cloud gateway Local access Bluetooth
Connected and offline doors operate within the same access strategy where supported. | Balances centralized visibility with local resilience, allowing different doors to use the connectivity level appropriate to their risk and infrastructure. | Requires clear door grouping, consistent credential rules, gateway planning, and testing of synchronization behavior during network outages. | Local emergency credentials can remain available if the network is unavailable. Mechanical override and battery replacement procedures should also be documented. |
| Access-Control System Integration | Commercial buildings that already use visitor management, video surveillance, identity systems, elevators, alarms, or centralized security software. | API SDK Wiegand OSDP
The exact interface depends on the lock, controller, and existing access-control architecture. | Reduces duplicate administration, supports unified identity and access workflows, and can link door events with broader security operations. | Compatibility must be verified before installation. Integration projects should address authentication, encryption, permissions, event mapping, and system availability. | The integrated system may support emergency unlock or lockdown workflows. Independent mechanical override and documented fail-safe or fail-secure behavior remain important. |
| Mobile Credential Deployment | Flexible workplaces, serviced apartments, hotels, campuses, and organizations that want to reduce the use of physical cards or keys. | Bluetooth NFC Mobile app
A smartphone can serve as a digital credential when the lock and phone support the required technology. | Fast credential issuance, time-limited permissions, reduced card replacement, and convenient access for employees, residents, guests, or contractors. | Users need compatible devices and adequate battery power. Mobile enrollment, phone loss, privacy, and credential revocation procedures should be defined. | Temporary PIN, physical credential, authorized backup phone, mechanical key, or staffed reception process can provide an alternative when a phone is unavailable. |
| PIN and Keypad Access | Shared offices, meeting rooms, equipment rooms, short-term rentals, and doors where issuing individual cards is inconvenient. | PIN code One-time code
Codes may be permanent, scheduled, temporary, or assigned to specific users depending on the system. | Enables keyless entry, supports temporary access, and avoids the need for users to carry a physical credential. | Codes must not be shared casually. Administrators should use unique or time-limited codes where possible and protect the keypad from observation and tampering. | Backup PIN, authorized physical key, emergency credential, or manual security assistance. Emergency codes should be controlled and audited. |
| Guest, Contractor, and Temporary Access | Building maintenance, cleaning services, deliveries, short-term guests, move-in periods, and scheduled service visits. | Time-limited PIN Digital key Visitor credential
Permissions can be restricted by door, date, time, or user role. | Improves accountability, limits access to the required period, and reduces the need to hand over permanent keys or cards. | Access windows, identity verification, cancellation, and event-log review should be included in the operating procedure. | A supervised entry process, temporary emergency credential, reception-managed access, or mechanical override may be used if the scheduled credential fails. |
| Emergency and Business-Continuity Mode | Fire, evacuation, power failure, network outage, cybersecurity incident, or urgent operational response. | Mechanical override Backup battery Emergency credential
The correct response depends on the door’s fail-safe or fail-secure design and local safety requirements. | Preserves a controlled path for authorized entry while supporting continuity during infrastructure or system failures. | Emergency behavior must be coordinated with fire-safety rules, evacuation plans, local regulations, and the facility’s risk assessment. Regular drills and testing are essential. | Use only approved emergency procedures, such as a fire-alarm release interface, mechanical key, backup power, emergency PIN, or authorized security response. |
