This module allows employee to approve/refuse their own leave requests, when their "Time Off" approver is themself.
auto_awesome What this module does
AI-generated from the code · Odoo 15.0Lets employees approve or refuse their own time off requests when they are set as their own time off approver, instead of being blocked by Odoo's normal rule.
In standard Odoo, an employee cannot validate or refuse their own leave request, even when they are configured as their own time off approver. This module changes that rule.
- It applies to time off requests (
hr.leave). - When a user tries to approve or refuse a leave, Odoo normally checks whether that user is allowed to do so. This module skips that check for the user's own request, but only when the employee linked to the user is also set as their own time off approver.
- Administrators are not affected: the normal behaviour is kept for them.
- The change only concerns the approval and refusal actions; it does not add new screens, menus, buttons or reports.
- No new fields, default values, emails or scheduled jobs are added.
In practice, an employee whose time off approver is themselves can confirm their own leave request without needing someone else to approve it. The module is installed from the Apps list under Human Resources and works together with the standard Time Off app.
Depends on
Models and fields (1)
- hr.leave · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 15.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/hr-holidays.
terminal Installation and usage
OCA documentation · Odoo 15.0Configuration
Source · Odoo 15.0Nothing to configure. When employee "Time Off" approver is set to himself, it will work as expected.
No verified information in OCA: Installation, Usage.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.