
How to Configure UniFi Access for Your Site
A door that opens for the wrong person, remains unlocked after hours, or cannot be released safely during an emergency is not a software problem alone. It is a site-security and life-safety issue. Knowing how to configure UniFi Access properly starts with a sound installation, a clear access policy and a network that has been designed to support the system.
UniFi Access can provide central control of doors, credentials, visitor entry and event records from a single management platform. For offices, schools, managed buildings and healthcare settings, that can reduce reliance on keys while giving authorised staff a clearer view of who entered, where and when. The configuration is straightforward once the physical door hardware, cabling and network are correct. Cutting corners at that stage tends to create faults that software settings cannot solve.
Before You Configure UniFi Access
Confirm that every door has been commissioned electrically before adding users or access rules. The lock type, door contact, request-to-exit device, reader, emergency break-glass unit and fire alarm interface must all work as intended. A controlled door must always allow safe escape in accordance with the applicable fire and building requirements. Access control should never prevent emergency egress.
This is particularly important when choosing between fail-safe and fail-secure locking. A fail-safe magnetic lock releases when power is removed, while a fail-secure electric strike remains locked when power fails, subject to its mechanical arrangement. Neither option is automatically right for every opening. The use of the door, escape route, fire strategy and any existing alarm system all need consideration.
The network should also be ready before the UniFi Access devices are adopted. Provide suitable PoE switching capacity, label every cable and allow enough power budget for readers, hubs, intercoms and any associated equipment. For a commercial installation, it is sensible to place access-control equipment on a managed network or dedicated VLAN, with only the required communication permitted to the UniFi console. This improves security and makes future fault-finding more efficient.
Check that the UniFi console running the Access application is current and has a reliable backup arrangement. The precise menu names can change as the platform develops, but the overall process remains the same: adopt devices, create doors, test hardware, add people and apply permissions.
How to Configure UniFi Access Step by Step
Adopt the controller and door hardware
Sign in to the UniFi console with an administrator account and open the Access application. The controller, access hubs, readers and intercom devices should appear as ready for adoption when they are correctly connected to the network and on compatible firmware.
Adopt each device individually, then give it a useful name. Use names that reflect the actual location, such as Main Reception, Ground Floor Comms Room or West Stairwell Level 2. Avoid vague labels such as Door 1. Clear naming is valuable when facilities staff need to review an event, revoke access or report a fault without visiting every door.
If a device does not appear, check PoE delivery, network addressing, VLAN allocation and firmware compatibility before resetting anything. Repeated resets may remove useful configuration information and do not resolve an underlying cabling or switching fault.
Create and test each door
Once the appropriate hub and reader are adopted, create the door within the Access application. Assign the reader, lock relay, door position sensor and request-to-exit input to the correct door. Where fitted, configure any intercom or secondary reader as part of the same entrance arrangement.
Set the lock behaviour according to the installed hardware and agreed operating policy. This includes how long the lock releases after a valid credential, how long the door may remain open before an alert is raised, and whether forced-open events should generate a notification. Reception doors may need a longer release time for visitors or wheelchair access, while a secure plant room generally requires a short release time and prompt door-held alerts.
Test each input and output at the door, not only in the software. Present a valid credential, use the request-to-exit button, open the door normally and simulate the conditions that should create an alert. Confirm that the door contact reports accurately. If the system says a door is closed when it is physically open, investigate the sensor position, cable termination and magnet alignment before changing software thresholds.
Set schedules before issuing credentials
Most sites do not need every door available to every person at all times. Define the working schedules first. A typical office may allow staff access from early morning until early evening, with restricted access outside those hours. A school may need separate schedules for teaching areas, administration spaces and out-of-hours facilities use.
Create schedules around how the building actually operates, including cleaning contractors, deliveries, shift workers and holiday closures. Where a door is intended to be free-access during reception hours, use an authorised unlock schedule only where it is appropriate to do so. Main entrances may require staff oversight or intercom approval even during the day.
Avoid relying on a single broad schedule for the whole premises. A well-planned system gives people access to the doors they need, at the times they need it, without giving them unnecessary access to sensitive areas.
Add users, groups and credentials
Add staff members to the Access application and group them by function rather than creating individual rules for every person. For example, you might create groups for office staff, warehouse staff, managers, cleaners and contractors. Assign each group the relevant doors and schedules, then place users in the appropriate group.
This approach makes changes manageable. When a new member of the cleaning team starts, they can be added to the existing group. When a contractor finishes work, their access can be removed without affecting other users. It also reduces the risk of inconsistent permissions developing over time.
Issue the credentials supported by the installed readers, such as NFC cards, key fobs or mobile credentials where the site policy and hardware allow. Record who has received each physical credential and set a process for reporting lost cards immediately. A lost fob should be disabled in the system rather than relying on someone to return it later.
Administrative permissions need the same care. Limit Access administrator rights to staff who genuinely need to change doors, users or system settings. Day-to-day reception staff may need visitor and credential functions without being able to alter door hardware configuration or unlock sensitive rooms permanently.
Configure visitor entry and intercom use
For sites receiving regular visitors, decide who will approve entry and what should happen if that person is unavailable. A reception intercom can call a designated user or group, but it should not become the only route into a building if reception is unstaffed at certain times.
Set visitor processes that match the risk level of the site. A small office might permit a host to release the main entrance remotely after confirming a visitor. A healthcare, education or multi-tenant environment may need visitors to sign in, wear passes and be escorted beyond reception. The technology supports the process, but it cannot replace a clear visitor policy.
Review alerts, logs and maintenance
Configure alerts for events that require action, including a door held open, forced entry, device offline status or repeated failed credential attempts. Too many alerts create noise and are quickly ignored, so prioritise events that a responsible person can investigate.
Review entry records periodically, especially after an incident or when access arrangements change. Audit logs can help confirm patterns and identify doors that are routinely propped open, but they should be handled in line with the organisation's privacy procedures and retention policy.
Plan maintenance rather than waiting for a failure. Check reader operation, door alignment, lock performance, backup power and network health at agreed intervals. Firmware updates should be assessed and applied in a controlled maintenance window, particularly on buildings where doors are in constant use.
Common Configuration Problems
A reader may show online while the door still fails to operate correctly. In many cases, the fault is at the door: an incorrectly configured lock type, weak power supply, damaged cable, poorly aligned contact or a mechanical issue with the latch. Treat the Access event log as one part of the diagnosis, not the complete answer.
Another common issue is overly generous permissions created during initial setup. Temporary access for installers, agency staff or contractors can remain active long after the work has ended. Set expiry dates where available and review temporary accounts routinely.
Finally, do not configure access control in isolation from the rest of the site infrastructure. Door entry, CCTV, WiFi, data cabling and network switching often share routes, cabinets and power provision. Coordinating those services from the outset produces a tidier installation and avoids disruptive alterations later.
For complex or occupied premises, professional commissioning is usually the sensible route. Net-Com SW can install and configure the cabling, network and door-entry components as one coordinated system, with testing that reflects how the building will actually be used. A properly configured UniFi Access system should make authorised entry routine, give managers useful control and leave no uncertainty about what happens when a door needs to remain secure.



