Absence detection access
hr_attendance_user_acl version 19.0.1.0.0 limits Odoo’s automatic absence detection to opted-in employees. It depends on base_user_acl and hr_attendance.
It does not give a user access to the Attendances app or restrict attendance records. It only decides whether the native Attendance: Detect Absences for employees scheduled action evaluates the employee linked to an internal user.
Enable tracking for one employee
- Open Settings > Users and select the internal user linked to the employee.
- In Access Rights > Access-control list, select Attendance Tracking and save.
- On the employee, confirm the linked user, current started contract, fixed-hours Working Schedule, and consistent time zone.
- In Attendances > Configuration > Settings, enable native Absence Management for the employee’s company.
The native scheduled action evaluates the preceding day. Its standard interval is every four hours; an administrator can run it through Settings > Technical > Automation > Scheduled Actions. Opening that Technical menu requires Developer Mode.
Eligibility conditions
Odoo includes an employee only when Absence Management is enabled for the employee’s company; the employee is active and linked to an internal user with Attendance Tracking; the current contract has started; the schedule is fixed-hours and includes work on the preceding day; and the employee, contract, and schedule use the same time zone. Odoo also skips days that already have an hr.attendance.overtime.line.
For an eligible missed shift, native Odoo creates a one-second technical attendance at local midnight and keeps it only when its normal overtime calculation is non-zero. Attendance Officers and Administrators inherit Attendance Tracking. To exclude one of those employees, change the native Attendance role rather than removing only its implied group.
Verify
With a non-production, fixed-hours employee linked to a test user, enable Attendance Tracking and Absence Management. Run the native job on the day after a scheduled day with no attendance, then check Attendances for the technical local-midnight entry. Remove the setting from an otherwise identical user and confirm no entry is created.
Related: shared access-control list and RWR Working schedules.