Cloud Access Control
System OEM Supplier
Mobile app management · audit records · multi-site scope · private or local deployment route · model-specific connection review. Standard supply 200 units; OEM/private label 500; ODM 1,000.
Management Route Features
Multi-Site Dashboard
Review multi-site scope, role permissions and status visibility against the selected account and controller configuration.
Mobile App Management
iOS and Android management app: add users, issue mobile keys, remote unlock, view live audit trail, receive instant alerts — from anywhere.
External connection review
Documented external-interface and event scope can be reviewed for a named workflow, controller and target system. Confirm the test method, version and delivery responsibility before supply.
Real-Time Audit Trail
Every access event (granted, denied, forced entry, tamper) timestamped and stored. Exportable audit reports for compliance, insurance, and incident investigation.
Private Cloud / On-Premise
A private or local deployment route can be reviewed for the customer's infrastructure. Confirm the deployment boundary, data location, privacy documents and operating responsibility in the written project scope.
Offline Resilience
Offline credentials, event buffering and reconnection behavior are confirmed against the selected controller and firmware.
Technical Specifications
Controller Hardware
| Doors per Unit | 1-door or 2-door controller configuration |
| Reader Interface | OSDP v2, Wiegand 26/34, RS-485 |
| Local Credentials | 100,000 |
| Local Event Log | 500,000 records |
| Network | 10/100M Ethernet (PoE optional) |
| Relay Output | 1 × Form C, 5A at 30V DC |
| Alarm Inputs | 4 supervised (REX, door contact, tamper, PIR) |
| Documentation route | CE (LVD, RED) and RoHS for EU supply. If a tender names EN 50131-1 or another standard, ask which documents are available. Confirmed per model, revision and destination before quotation. |
Management Route
| Deployment | Hosted (EU DC), Private cloud, On-premise (Docker) |
| External interface | Named interface or event scope by model and deployment |
| Mobile App | iOS 14+ / Android 10+ (white-label available) |
| Users per Account | Confirmed by account and project scope |
| Sites per Account | Confirmed by account and project scope |
| Service terms | Confirmed in the written deployment scope |
| Security documents | Requested and reviewed for the selected deployment |
| Access roles | Role and authentication route confirmed by model and account |
OEM Cloud Access Control
White-label mobile app, branded management route and external connection scope are reviewed under the OEM/private-label programme. Private or local deployment is confirmed through the written project quotation.
Cloud Access Control — Common B2B Questions
Traditional access control stores credentials and audit logs on a local server, while a cloud route moves selected management functions to a hosted service. Confirm local-door behavior, offline fallback, data location, update responsibility and multi-site scope for the exact controller and deployment. If a named HR, property-management or building workflow must connect, review the documented interface and acceptance workflow rather than assuming a universal connection.
A hosted, private-cloud or on-premise route can be reviewed for the selected controller, account and destination. Confirm the storage region, data roles, offline behavior, deployment responsibility and security documents in the written project scope; do not assume one hosting route satisfies every GDPR or sector requirement.
External interface documentation, event scope and connection boundaries can be reviewed for the selected controller and deployment. Name the required user, credential, event or door action and the target HR, property-management, co-working or BMS workflow; confirm the test method, version and delivery responsibility before calling the connection ready.
Site, door and credential capacity depends on the selected controller, account configuration and deployment. Role-based permissions, multi-site visibility and any reseller or white-label boundary can be reviewed for the named project; confirm the required limits and data separation in the written scope.
Local-door behavior, cached credentials, event buffering and reconnection handling depend on the selected controller and firmware. Confirm which credentials and schedules remain available during an outage, how records are retained, and how changes are reconciled before deployment.
Branding, dashboard, mobile-app, account and deployment options can be reviewed for the selected OEM scope. Confirm the requested assets, account ownership, data separation, documentation, support responsibility and any platform terms in the written agreement; no universal white-label package is assumed.
Security controls and documents depend on the selected hosting route, controller and destination. Request the current encryption, access-control, logging, vulnerability-management and data-processing evidence for the exact deployment; certification or audit status must be confirmed in writing rather than inferred from a product label.
Cloud access control brief: interface, power and account ownership
A cloud access-control deployment should be compared by controller, reader interface, power, network and account owner. Use the model page's documented values as the starting record, then validate the site workflow.
Checks before shortlisting
- OSDP, Wiegand and RS-485 are chosen against the panel, reader and security workflow.
- 26-bit and 34-bit credential formats are recorded with card source and fallback method.
- PoE, the 5A at 30V DC relay rating and backup ownership are checked against the actual controller and lock load.
- The 10/100M Ethernet link, VLAN, cloud route and account roles are assigned to the network owner.
- The pilot doors and the standard, OEM or ODM order route are kept distinct.
- CE and RED references are tied to the supplied SKU and market file.
- Audit events, admin roles, credential import, offline behaviour and RMA are acceptance fields.
Implementation and handover
- Map readers, doors, lock release, REX, power and controller location.
- Test credential, denied event, door release, offline behaviour and cloud recovery.
- Record interface, bit format, firmware, account owner and permission model.
- Attach power, network, security and market documents to the selected revision.
- Hand over credentials, logs, training and RMA route before a larger door count is released.
Risks to resolve before supply
- A cloud label does not prove offline behaviour or a local release path.
- A 26-bit or 34-bit format can fail when the card source and panel expectation differ.
- PoE and the 5A at 30V DC relay rating require a load and recovery check at the actual door.
- Unclear account ownership can block audit access after the installer leaves.
Before requesting a quote
Choose the cloud route when interface, load, network, account and audit events pass the same controller test. Keep the model record with the project RFQ. Share the selected model, configuration and destination market through the project RFQ route.