09:12 HR posts the exit as effective
Employment flips to exited, the role pack dies, visitor bookings void.
One class of incident is common: employment ended, the card is still in a bag, or the face is still on the controller allow-list. Admin thinks “the system will stop it.” The access vendor thinks “HR will tell us.” In the empty hours, the gate honors old rights.
09:13 Sync gates / controllers
The list ships to every door. Failure retries and alerts admin—it does not silently succeed.
If not hooked up: still swipes in at 15:40
The card is still in the vendor app. Nobody remembers to delete it. The parking barrier opens too.
09:14 The trail is auditable
Later swipes should refuse and keep a fail record for safety and internal audit.
Access and attendance only
Card numbers live in hardware; the roster lives in Excel. Role changes are verbal; exits depend on memory.
Hooked to HR master data
Employment, role and zone are one list. Gates execute; they do not hide rights.
Death of rights needs master data, not another gate
You can name the hardware brand; software must write the list and read events. Access and attendance only, with no business hookup: Access control and attendance only, with no business hookup. How park gates and parking connect to HR: How park gates and parking connect to HR. Rights and org structure can be planned with management systems: Management Systems.
Visitors and contractors leak more easily than employees
Employees at least have an exit process. Visitors are often “whoever brought them.” They need expiry, escort zones, and auto death. Face and trail retention is a separate write-up: Face and location data: how privacy is handled. Audits will sample these records: What device records must prove in a safety audit.
A failed sync must be visible
If a failed list-push only sits in a gateway log, admin thinks the card is already dead. Failure should open a ticket or at least notify—the same discipline as alerts becoming tickets: Fewer screens to watch: how alerts become assignable tickets. DaXi Technology puts access events and employment on one chain. To join existing gates to the roster, go to the Hardware-software service page and name the brand and how you delete a card today.
A role change is easier to forget than an exit
An exit at least has paperwork. A role change is often a chat message: shop floor to warehouse, zones unchanged, a special-work cert expired but the gate still knows the face. Ship rights from a role template, not by ticking points on a controller. Template changes must replay so an audit can ask why they still entered the hazmat store that day.
If parking, elevator control and the server-room door are each a closed box, the HR hookup breaks at the second door. You can name brands, but the exit must be one rights service: Must we supply the hardware, or can you name the brand and Closed box vs. open access: which one can enter a work order. Among gains you can see, rights that follow the role is the first HR will admit: Hardware-software gains you can actually see.
Instant death has a hidden condition: HR status must be true. If employment flips only after payroll, access lags by days. Bind “rights off” to the exit submit or last day, not payday. If the protocol will not push a deny list, a new gate still cannot die in minutes: If the device protocol is closed, can we still integrate.