Connecting an online booking platform to physical room access - so a confirmed reservation automatically becomes a valid entry credential, with no staff intervention required at the door.
SCAPE Singapore is a youth community hub operating multiple bookable rooms and facilities for public use. With reservations managed through Salesforce and physical entry controlled by ZKTeco hardware, the facility faced a recurring operational problem: the two systems were completely disconnected. Every check-in required staff to manually verify bookings before granting access. Securevision was engaged to design and implement the middleware layer that would close this gap permanently.
| Client | SCAPE Singapore |
|---|---|
| Location | Orchard, Singapore |
| Sector | Civic - Youth & Community Hub |
| Project Type | Custom Systems Integration |
| Scale | Multiple bookable rooms across the facility; QR code reader at each room entry point |
SCAPE managed room reservations through Salesforce and physical entry through ZKTeco access control hardware. The problem was that these two systems operated entirely independently. A completed booking in Salesforce had no connection to the door reader outside the booked room. Every check-in required a staff member to manually verify the reservation and then grant access - creating operational overhead, queues during peak periods, and a permanent dependency on personnel being present at each entry point.
The access control system had no awareness of who had booked what, or for how long. There was no mechanism to enforce time-bound entry - a user with a two-hour booking could remain beyond their slot without the system detecting it. The audit trail for room usage was also fragmented: bookings lived in Salesforce, access events lived in ZKTeco, and there was no automated link between the two records.
SCAPE needed more than a process improvement. They needed the two systems to function as a single connected workflow - where a confirmed booking automatically generates a valid, time-limited entry credential and delivers it to the user, without any staff involvement at any stage.
| Operational Area | Before Integration | Securevision Integration |
|---|---|---|
| Booking-to-entry link | Manual - staff must verify each reservation before granting access at the door | Automatic - confirmed booking immediately triggers credential generation with no staff action required |
| Access credential | No credential issued - entry dependent on staff recognition or printed confirmation | Unique, time-bound QR code generated per booking and delivered automatically to the user via Salesforce |
| Time enforcement | Not enforced - no system mechanism to restrict access to the booked slot | Enforced at the reader - QR code is valid only for the booked room within the booked time window |
| Manpower at entry | Staff presence required at each access point during all booking periods | Self-service - no staff required at the door; users scan and enter independently |
| Audit trail | Split across two systems - booking record in Salesforce, access event in ZKTeco, no link between them | Unified - booking, credential issuance, and door events linked through the middleware layer |
The options on the table ranged from replacing the entire booking system with a purpose-built facility management platform, to building a lightweight integration layer that allowed both existing systems to continue operating without modification. SCAPE had already invested significantly in Salesforce for customer management, and the ZKTeco hardware was functioning correctly at every room. The problem was not the systems - it was the gap between them.
Securevision recommended building a custom middleware layer that sits between Salesforce and ZKTeco - receiving confirmed booking data from Salesforce, applying access rules and time-validity logic, generating QR credentials, and pushing them to the ZKTeco system. Neither platform required modification. The middleware handles all orchestration. This approach preserved the existing investment in both systems while solving the integration problem completely.
This architecture is also resilient to future change. Because neither Salesforce nor ZKTeco was altered, both continue to operate on their own native logic. If either platform is later upgraded or replaced, the middleware layer can be updated independently. The integration is loosely coupled by design - each component can evolve without dismantling the others.
Securevision designed the integration as a four-stage automated workflow, with the middleware acting as the intelligence layer between booking confirmation and physical door entry. The design requirement was that no stage should require human input once a booking is confirmed and approved.
The user accesses the SCAPE booking portal via Salesforce, selects a room, date, and time slot, submits payment, and awaits approval where required. This stage is entirely within Salesforce with no change to the existing booking experience.
Once a booking is confirmed, the middleware receives the booking data from Salesforce, applies the defined access rules, assigns time validity and room permissions, and generates the credential parameters to be pushed to ZKTeco.
A unique, time-bound QR code is generated - linked to the specific room and valid only within the booked window. Salesforce handles delivery to the user automatically. No staff action is required at this stage.
At the facility, the user scans their QR code at the ZKTeco reader. The system verifies the credential in real time against the booking record. The door unlocks only if the room, time, and credential all match. Access outside the booked window is automatically denied.
The four stages operate as a single continuous flow with no manual handoffs. From the moment a booking is confirmed, every subsequent step - credential generation, delivery, verification, and entry - is handled by the integrated system.
Rather than treating booking software and access control as separate problems, Securevision engineered a single flow where digital intent - a confirmed reservation - translates directly into physical action: an unlocked door.
Salesforce manages the full customer-facing workflow: the booking portal, approval routing, payment processing, and automated delivery of the QR code to the user once the credential is generated. No changes were made to the existing Salesforce configuration - the middleware consumes its output.
Entry Access Control →The middleware is the core of the solution. It receives confirmed booking data from Salesforce, applies access logic - which room, which user, which time window - generates the credential, and pushes it to ZKTeco. It is the intelligence layer that neither Salesforce nor ZKTeco provides natively.
Platform & Management →ZKTeco QR code readers at each room entry point verify the credential in real time at the moment of scan. The reader checks room, user, and time window before unlocking. Entry outside the approved window is denied automatically, without staff involvement.
Entry Access Control →ZKTeco QR code readers at each bookable room entry point, integrated with a custom middleware layer built by Securevision to bridge Salesforce and the ZKTeco access management platform.
Readers: ZKTeco QR code readers deployed at each bookable room entry point across the facility.
Management Platform: ZKTeco access management platform integrated with the Securevision middleware via API.
Core function: Securevision-built middleware orchestrating all data exchange and logic between Salesforce and ZKTeco.
Architecture: Loosely coupled design - neither Salesforce nor ZKTeco required modification. Each system operates on its own native logic; the middleware translates between them.
Every step from online booking to physical door entry is automated. No staff intervention is required between a user's confirmed reservation and their arrival at the room.
Staff are no longer required to be present at each access point for manual verification. Operational overhead at the facility is materially reduced during peak booking periods.
Users receive their access credential automatically after booking confirmation. Arrival is fast and self-service - scan and enter with no queues or check-in counters.
QR codes are valid only for the booked room within the booked time window. Access outside the approved slot is automatically denied without staff needing to monitor or intervene.
Booking records, credential issuance events, and ZKTeco door logs are all linked through the middleware - a complete record of who accessed which room, and when.
Additional rooms, facilities, or separate venues can be added to the same integration framework without rebuilding the core system. The middleware architecture is not site-specific.
Most facilities that operate bookable spaces already have the two components they need: a booking platform and access control hardware. What they are missing is the connection between them. That gap - where a confirmed booking exists in software but has no effect on a physical door - is where the operational cost accumulates. It manifests as staff time, queuing, and inconsistent enforcement. We built the middleware for SCAPE because the problem was not the systems they had chosen; it was the absence of a layer that made them work together. This same model applies wherever reservation and physical access need to operate as one.
Every project Securevision delivers draws on multiple systems working together - cameras, access control, intercoms, vehicle management, network infrastructure, and platform software. The cards below show the full range of systems we design and install. Each one links to a deeper explanation of how it works, when it is needed, and what to look for when specifying it.
If you manage bookable spaces and want to remove manual coordination at the point of entry, we can design the right integration for your platform and hardware.