Access levels group doors; schedules set the times they apply; holidays override normal days. Anti-passback stops one card being passed back to let a second person in. Audit logs record every event, so you can see who went where and when, and spot doors forced or held open.
Key takeaways
- Access levels + schedules = who, where, when.
- Anti-passback needs readers on both entry and exit.
- Logs are only useful if someone reviews them.
- Joiner/leaver process: disable access the day someone leaves.
01Building the rules
| Rule | Example |
|---|---|
| Access level | "Finance" = main door + finance office |
| Schedule | Mon–Fri 07:00–19:00 |
| Holiday | Public holidays: staff doors closed |
| Special users | Security: all doors, 24/7 |
| Temporary | Contractor: store room, 2 weeks, working hours |
02Anti-passback
Anti-passback stops a card being handed back through a gate for a second person. It needs readers on both sides (entry and exit). Useful at staff gates, car parks and turnstiles.
03Logs and reports
- Who entered which door and when
- Denied attempts (wrong time, wrong door, disabled card)
- Doors forced or held open
- Reports for investigations and attendance
04Frequently asked questions
What is anti-passback?
A rule that stops a credential being used to enter twice without exiting in between, so it can't be passed back to someone else.
How long are access logs kept?
It depends on the system's storage and settings. Export logs you need for investigations.
Can access control give attendance reports?
Access logs can support attendance, but a dedicated time attendance system handles shifts, overtime and payroll better.
