Time off approvals, finally transparent and under control
Give employees and managers clear, timely notifications on every request, and give HR the advance-notice, blackout and governance rules to keep Time Off predictable — all without writing a line of code.
Odoo’s built-in Time Off sends the same generic status email to everyone, offers no way to enforce notice periods, blackout windows or a no-self-approval rule, and forces HR to reconstruct after the fact who approved what — and why a request was refused.
Leave Notifications & Governance adds a full communication and policy layer on top of Time Off: audience-specific notifications, configurable advance-notice and blackout rules, mandatory refusal reasons, self-approval prevention with escalation, and bulk actions — all wired directly into the request you already use.
Everything Time Off governance needs
Every capability below is implemented in the module.
Lifecycle Notifications
Submission, approval and refusal each push an in-app inbox notification to the right audience — employee, approver or HR — gated by a simple company toggle.
Advance-Notice Enforcement
Require a minimum number of days between a request and its start date, per leave type, with a warn or hard-block mode.
Maximum Continuous-Days Limits
Cap how many consecutive days a single leave type allows, and choose whether a breach only warns or blocks the request outright.
Blackout Periods
Define company-wide or department-scoped date ranges where time off is restricted, each with its own warn-or-block enforcement.
On-Form Policy Warnings
A warning banner explains exactly which rule a request brushes up against — notice window, day limit or blackout — before it is even submitted.
Refusal Reasons & Wizard
Refusing a request opens a guided wizard backed by a reusable preset library, so the employee always receives a clear, permanent explanation.
Self-Approval Prevention & Escalation
Approvers can never approve their own request; when no other approver is available, the request automatically escalates to a configured fallback officer.
Manager Override with Audit Trail
Managers can override a policy block for genuine exceptions, but only with a mandatory justification that is tracked in the request’s chatter.
Bulk Approve & Refuse
Approve or refuse-with-reason multiple requests at once from the Time Off list, without opening each one individually.
How it works
Set the rules
Configure advance-notice, maximum-days and blackout policies per leave type and department, and pick a company escalation officer.
Employees request
A request is checked against the active rules in real time — compliant requests submit normally, borderline ones show a clear on-form warning.
Managers decide
Approvers are notified instantly, self-approval is blocked, and refusals require a documented reason before the request can close.
Everyone stays informed
Employees see approvals and refusals — with the exact reason — the moment a decision is made, right in their Odoo inbox.
See it in action
Ten screens covering governance configuration, the day-to-day request flow and company-wide settings.
Configure advance-notice and maximum continuous-day rules per leave type, with warn-or-block enforcement modes.
Define company-wide or department-wide blackout periods and see the enforcement mode of each at a glance.
Set blackout date ranges, optional department scoping and a warn-or-block enforcement mode for each period.
Maintain a reusable library of refusal-reason presets so managers never retype the same explanation.
Write the message once, reuse it everywhere: each preset carries the exact text the employee will see.
Employees see a clear on-form warning the moment a request brushes against a notice or blackout rule.
Every refusal keeps its reason and explanation permanently on the request for the employee to see.
Refusing a request opens a guided wizard that enforces a documented reason before it can be closed.
Bulk refuse-with-reason and bulk approve straight from the Time Off list, with no need to open each request one by one.
Toggle notification events on or off and set the escalation officer for the whole company from Settings.
Frequently asked
Does this replace Odoo’s native Time Off approval flow?
No. It extends the existing Time Off workflow with notifications, governance rules and a refusal wizard — your current approval flow, leave types and allocations keep working exactly as before.
Can different leave types have different rules?
Yes. Advance-notice requirements and maximum continuous-day limits are configured per leave type, each with its own warn or block enforcement mode.
What happens if a manager needs to override a blocked request?
The manager marks the request as overridden, but only after entering a justification, which is recorded and visible in the request’s audit trail.
Where do notifications appear?
As in-app inbox notifications routed to the employee, the approver or the configured escalation officer, depending on the event and your company’s notification toggles.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Notifications, advance-notice rules, blackout periods and refusal governance for Odoo Time Off — all in one app.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Time Off (hr_holidays)
• Calendar (calendar) • Employees (hr) • Discuss (mail) |
| Lines of code | 558 |
| Technical Name |
cerevantix_leave_notifications |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module