Many parks spend on gates and faces, then stop software at the vendor attendance sheet. HR onboards in another system, security types faces in the access console, payroll uses paper exception slips. Three teams, three books. Newer gates only make the island more stable.
Instant death of exit rights is the stretch access should hand to HR: Access control tied to HR. How park parking and people join the org: How park gates and parking connect to HR. If the face gallery is not layered, the island also piles sensitive data: Face and location data: how privacy is handled.
“Can punch” is a pass, not a management system
Access-only can satisfy “there is hardware at the door.” It cannot: block a shop after a role change, auto-kill a contractor pass, or match night shifts to access logs. Treat the system as a monitor wall vs. a work entry—the same split applies to access: Treating the system as a monitor wall vs. a work entry. If exceptions only pop in the guard room, the path is still not hooked up: With devices in the business vs. without.
A thin phase-one budget is not a reason to build a forever-separate attendance box. At least join hire, exit and visitor expiry to org master data. Contractors and interns expose the island: the person left, the gate still treats them as staff; a warehouse-to-QC move leaves the shop door open. Guards wave through a familiar face; an audit cannot prove rights follow the org.
DaXi Technology designs access by role, not by stacking features per gate. To land the island, go to Hardware-Software Integration and name the access brand and HR system you have.
Rules live in HR. Access only supplies events
A guard who leaves a door “always open” or shares an admin card turns the island into a hole. Rights audit beats device-online rate. If flex, overtime and field rules live in the access vendor, every roster change is dual maintenance—rules in HR, events from access. Multi-park copies the island; unify people master data before you add gates.