Use Signage at the door
One resource, its booking window and the right credential for the person entering.
Before you begin
- Use an Access-mode device bound to the room’s exact resource.
- Verify the controller, authorisation checks and booking-window enforcement before use.
- Keep visitor credentials private and confirm the installation’s reader instructions.
Product design guide: these are the required Signage workflows, not a claim that every step exists in the reviewed overview branch. Check the rollout guide and your installed build before use.
Step by step
Confirm the room and time
The doorway screen shows occupancy for its bound resource and the relevant booking window. A booking in a different room or outside this window must not authorise this door.
Use the visitor or member route
Visitors use a personal BookingAccess QR for their visit, not the overview’s booking-page QR. Members use the Hik face reader, not that visitor QR. Only show the visitor-specific credential in the intended authorised flow; do not publish a reusable shared door credential.
Check the access decision
The door integration must resolve the credential, match the resource and booking window, then open or deny the lock. Entry must be denied before the booking starts and after it ends. A tap, visible QR or sent command is not proof that the correct door opened.
Keep the doorway focused
Access mode has no floor map, in-room meeting join or advertising. If those appear, ask the operator to check the saved mode and resource before continuing.
You’re ready when
The correct person can enter only the assigned room during the permitted booking window, with a verified door result.
Troubleshooting
- The QR opens a booking page
- That is the Overview QR. Do not use it as a door credential. Check that Access receives the visitor’s personal BookingAccess code.
- An early, expired or different-room booking opens the door
- Stop relying on this access flow and have the installer correct and retest the credential, resource and time-window enforcement.
- A member is asked to use the visitor QR
- Check Hik face enrolment and the member access integration. The visitor QR must not become the member credential path.
Technical details
- Required access checks
- Validate the person or BookingAccess credential, the exact resource, the active booking window and the controller result. Test early, expired, wrong-resource and unauthorised attempts.
- Excluded controls
- No floor plan, meeting join or advertising. In-room service actions do not belong on this doorway display.
Common questions
- Is BookingAccess the same as a booking-page QR?
- No. The overview link starts member booking. BookingAccess identifies the visitor’s authorised visit and needs its own access validation.
- Does a successful command prove entry?
- No. Check the physical door and controller result. A display message alone is not proof of lock operation.
Still stuck? Tell support what happened and which step you reached.
Email support