Advanced lesson
Commission Door Access with an Acceptance Record
Turn an approved door design into a documented test plan that covers permissions, events and failure behavior.
Reviewed September 2026 · 3 minute read
A green reader is only one check
| Test category | Evidence to collect |
|---|---|
| Permission and schedule | Approved credential grants entry; unapproved, revoked and out-of-schedule cases are denied as designed. |
| Door state and events | Verify actual door position, required held/forced events and intended alarm/notification routing. |
| Network or server interruption | Record the approved offline credential, synchronization and event-storage behavior. |
| Power and required egress behavior | Qualified parties test the approved design under controlled conditions and record results. |
| Recovery and handoff | Restore normal service; confirm clock, event history, privileges, schedules and owner training. |
Agree on authority, safety arrangements and timing before any live interruption. Practice control logic on an approved bench rig; do not improvise a power-cut or lock test on an occupied exit.
Ask what protects each part of the path
The credential, reader-to-controller connection, controller network and administrator account have separate security properties. OSDP supports supervised communication; Secure Channel adds protection when correctly supported and configured. Do not assume encryption is active because a device advertises OSDP.
Use compatible verified devices and the vendor’s secure commissioning procedure. Record that Secure Channel is enabled and commissioning/default keys are handled appropriately, without placing secret keys in the public handoff. Reader-link protection does not automatically strengthen a weak credential technology.
Keep the result tied to the door
Worked example
A contractor credential still works outside its intended schedule
Record the door ID, credential role, relevant schedule/time zone, controller status, expected denial, observed grant and event reference. Investigate the actual permission path rather than hiding the failure with a new label.
After an approved correction, repeat the affected allowed and denied cases, synchronization checks and required safety checks.
Write a bench acceptance record
Use a test controller and simulator or bench components authorized for training. Plan one permitted credential, one denied credential, one expiry and one door-state input. Write expected results before trying them, then keep actual results and open issues.
When is the handoff complete?
When the agreed checks have evidence, unresolved items have owners and disposition, and qualified parties have verified the applicable real-door and egress requirements. A bench result does not certify an installed exit.
A ten-minute exercise: read the access test record
Practice case: a contractor needs Door A on weekdays, 9 a.m.-5 p.m., through Friday. Camera viewing is a separate permission. Use this paper exercise or an authorized simulator; it does not require changing a real door.
| Test | Expected | Observed |
|---|---|---|
| Tuesday 10 a.m., Door A | Granted | Granted |
| Tuesday 10 a.m., Door B | Denied | Denied |
| Saturday 10 a.m., Door A | Denied: grant expired | Granted |
| Contractor opens camera viewer | Denied unless separately approved | Denied |
Which result prevents acceptance? Identify the owner, the evidence to preserve and the next investigation. A grant event does not by itself prove that someone passed through or that the door secured afterward.
See the worked response
The Saturday grant fails the approved permission plan. Preserve the timestamp and event, then check the access group, expiry, timezone, controller synchronization and documented offline behavior. Correct the approved configuration in the controlled environment and repeat the relevant tests. Keep a separate record for the real door’s physical behavior, owned by the qualified project team.
Download the camera and door-access worksheet for a blank plan and a completed practice record.
Put it into practice
Check what you learned
Choose an answer for each question, then check your understanding. Your answers stay in this browser.
Read the answers and explanations
- A supported configuration and commissioning evidence confirm the active secure connection.
Protocol capability and the security mode actually in use are separate checks.
- An authorized bench setup or simulator with a written test plan.
Begin with a controlled practice environment. Real-door changes need qualified ownership and an approved plan.
- Record the event and investigate permissions, synchronization and offline behavior, then retest.
Keep the evidence and find why this path still grants access. Acceptance needs the required result at each in-scope opening.
Sources and further reading
- SIA: Open Supervised Device Protocol
Explains supervised reader/controller communication and Secure Channel. Verify both equipment support and the deployed secure configuration.
- Ubiquiti: Access hub terminal functions
Distinguishes lock outputs and sensor inputs on supported hubs. Follow the exact model instructions and approved door design for real work.
- OSHA: exit-route door requirements
Section 1910.36(d) addresses exit-door operation. It is one applicable reference, not a substitute for project-specific building, fire and accessibility review.
Keep your momentum
Ready for the next step?
If you can explain the example and your answer, try the next lesson. Revisit the feedback whenever you need it.
FryAVSI · Updated September 10, 2026
Reference this lesson or use a section’s direct link for a particular chart or example. How to cite an example.
FryAVSI · Northeast Ohio and beyond
Turn the learning into a working result.
Share the site, the requirement and the next step with our team.