Why this matters
Start with the relationship between people, roles and doors rather than with the number of keys. A diagram or matrix makes unintended cross-access visible before cylinders are configured.
What to confirm
Each door identifier, cylinder and key group must be linked unambiguously. More hierarchy increases the need for controlled records, issue procedures and a clear owner for approvals.
A practical working method
Apply least privilege to every level and test the matrix with realistic duties, absences and emergency situations. Plan capacity and coding rules for likely expansion before the initial order is finalized.
Records, acceptance and handover
Acceptance must test both positive and negative permissions: keys should open the intended doors and fail at doors outside their scope. Record issuance, return, loss and approved changes throughout the system's life.
Evidence and scope
This article is intended for preliminary product and project discussions. Product functions, performance, certification, compatibility and availability must be checked against current documentation for the selected model and the actual project requirements. Application examples are not claims of completed customer projects.