Manage entry / Access control guide
Access control helps you decide who may use a door and when. A successful project includes the physical door, the electronics, the software, and a clear process for managing people.
Start with the door schedule
List each opening you want to control. Note who uses it, normal business hours, deliveries, visitors, and any restricted areas. Decide whether staff need access outside working hours and whether doors should unlock automatically during a schedule.
Look beyond the reader beside the door. The lock, door closer, hinges, frame, power supply, wiring, controller, exit hardware, and door-position sensor may all affect the final scope. Existing mechanical problems should be identified before installing electronics.
Compare credentials around everyday use
| Option | Questions to ask |
|---|---|
| Cards and fobs | Which credential technology is used? How are lost credentials disabled? What do replacements cost? |
| Mobile credentials | Which phones and operating systems are supported? Is a personal phone required? What is the alternative for staff without one? |
| PIN codes | Can each person have an individual code? How are sharing, changes, and shoulder-surfing risks managed? |
| Visitor or temporary credentials | Who issues them, when do they expire, and how is visitor identity checked? |
Choose around your staff and operations rather than assuming one credential type is always best. Ask how credentials are protected against copying and whether existing cards can be reused without weakening the intended security.
Cloud management and local control
A cloud-managed service can simplify remote administration, particularly across several locations. A locally managed platform may give you direct control over servers and software. Both approaches require attention to maintenance, user permissions, support, and long-term cost.
Internet loss and power loss are different events. Some controllers store credentials and rules locally; remote administration or mobile features may still be affected. Door behavior during a power interruption depends on the hardware, design, backup power, and applicable requirements. Obtain a written explanation for the proposed system.
- Do existing credentials keep working if the internet is unavailable?
- Can schedules run locally, and how long are events stored?
- Which mobile, visitor, and remote-unlock features require connectivity?
- What happens at each opening when power is lost?
- How is backup power sized, tested, and maintained?
Make administration part of the design
Use an individual credential for each person and assign access according to their job. Limit administrator permissions, review access regularly, and remove access promptly when someone leaves. Name a backup administrator so routine changes do not depend on one person.
Decide how vendors, cleaners, and temporary staff receive time-limited access. Document who approves after-hours changes and how you handle a lost credential. Keep a secure record of system ownership and recovery procedures.
Understand what the event log proves
A credential event can show that a credential was presented or that a door changed state. It does not necessarily prove the identity of the person who entered or that only one person passed through. Shared credentials, held doors, and tailgating can undermine the intended result.
Ask whether the proposed system reports doors held open, forced-door conditions, and relevant equipment faults. Decide who receives those events and how they respond. Integrating video may provide additional context, but should be tested using the actual platforms and licenses.
What belongs in the quote?
- A door-by-door equipment and installation schedule
- Necessary lock, frame, closer, electrical, and network work
- Credential quantities and replacement pricing
- Software, subscription, mobile credential, and support fees
- Required integrations, licenses, and any work by others
- Ownership of hardware, accounts, configurations, and event data
- Training, documentation, acceptance testing, and ongoing maintenance
Test before handover
Have the installer demonstrate ordinary access, denied access, scheduled behavior, door-held events, and agreed outage scenarios. Practice adding a user, removing a user, and finding an event. Receive the final door schedule and service contacts, and confirm your business has the agreed administrative control.
Further reading
Brivo’s access control overview describes one manufacturer’s cloud approach and local controller operation. It is an example, not a universal description of every access system. Compare the proposed equipment’s own documentation.