Building access
Building access control: how to choose a system
Choosing access control starts with the building: its doors, its occupants and the people responsible for managing them. A reader catalogue cannot answer those questions.
The decision
Start with a door schedule
Building access control combines credentials, rules and connected door equipment to determine who may enter each area and when. List every controlled entrance and the people who need it: residents, employees, visitors, cleaners and contractors. Record the opening hours, existing lock or operator, reader, power supply and network connection. Include the garage and service entrance.
That schedule becomes the basis for comparing systems. Lexoh connects credentials, permissions and compatible entrance equipment in Security Center; the equipment and operating rules still need to be specified for each opening.
Separate identification, authorization and door movement
A credential identifies a record. The access system checks its permissions, and a controller sends the command to the connected lock or operator. A successful credential read does not establish that the person has access, or that the door physically opened.
Ask the supplier to demonstrate an allowed entry, a refused entry and the event each produces. Where door-position monitoring is needed, include the required sensor and wiring in the scope.
On a narrow screen, scroll the table horizontally to see every column.
| Field | Buying question | What to record |
|---|---|---|
| Entrance and users | Which doors and user groups belong in the project? | Named door, area, authorized groups and hours |
| Existing equipment | What can be retained after inspection and testing? | Lock/operator, reader, controller, power and network |
| Required records | What must the team be able to verify? | Credential decision; physical door state only with suitable monitoring |
| Responsibility | Who changes permissions and handles faults? | Administrator, installer, network contact and service scope |
Choose credentials around the people using them
Cards and fobs suit repeat users when compatible readers are installed. Temporary credentials can suit visits with a defined end time. Vehicle lanes may use plates, tags or another supported method, with assistance for exceptions.
Test existing credentials before committing to reuse. Matching the radio frequency does not establish compatibility: technology, encoding, security configuration and the reader interface also matter. Include issuance, replacement and revocation in the demonstration.
Compare cloud and local responsibilities
Cloud management can give authorized staff a common view across buildings. A local server changes who maintains the hosting, backups and updates. Neither label, by itself, tells you what happens at a disconnected door.
Request a written outage matrix. Identify which controllers retain which permissions, whether new changes can reach them, what events are stored and how recovery works. Test power loss separately from internet loss. Emergency release and egress must follow the approved building design.
Compare complete proposals
Price the same doors, credentials and workflows in each proposal. Separate equipment, wiring, installation, software, migration, training and ongoing support. Assign responsibility for account administration, network maintenance and physical repairs.
Before acceptance, test a lost credential, an expired visitor, an employee changing roles and a network interruption. Keep the results with the door schedule so the next manager can understand how the building operates.
Questions
Practical questions
Is a reader and a cloud account a complete door-access system?
No. The proposal must also address the controller, lock or door operator, power, wiring, network and any required monitoring or protective equipment. Ask who supplies and installs each part, and which existing components have been tested for reuse.
What should the team receive at handover?
Request the final door list, assigned administrator roles, credential-issuance procedure, tested outage behavior and service contacts. Keep the acceptance results and equipment instructions available to the staff responsible for the building; arrange a demonstration of the tasks they will perform.
Can existing readers stay?
Possibly. Confirm their model, interface, credential support and condition, then test samples with the proposed controller.
Does cloud access control require internet for every entry?
Not necessarily. Local decisions depend on the chosen controller and stored configuration; verify the exact offline behaviour before purchase.
References and further reading
- Building access control
Lexoh product or project reference.
- Cloud or on-premise
Lexoh product or project reference.
Your project
Plan the building upgrade
Share the door list and existing equipment with Lexoh to define compatibility, installation and operating responsibilities.
Discuss the project