Skip to Content
Menu

Time Off Leave Project Manager / Department Head Approval

by
Odoo

127.17

v 18.0 Third Party 9
Live Preview
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Time Off (hr_holidays)
Calendar (calendar)
Employees (hr)
Discuss (mail)
Lines of code 167
Technical Name hr_leave_approval
LicenseSee License tab
Websitehttp://www.probuse.com
Versions 11.0 12.0 13.0 14.0 15.0 16.0 17.0 18.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Time Off (hr_holidays)
Calendar (calendar)
Employees (hr)
Discuss (mail)
Lines of code 167
Technical Name hr_leave_approval
LicenseSee License tab
Websitehttp://www.probuse.com
Versions 11.0 12.0 13.0 14.0 15.0 16.0 17.0 18.0

Project Manager & Department Head Approval for Employee Leave Requests in Odoo

Employee Leave Request Approval by Project Manager or Department Head in Odoo

HR Holidays & Time Off Approval by Project Manager / Department Head

HR Leave (Holidays & Time Off) Approval Workflow for Odoo

Enhanced Odoo Leave Approval: Project Manager & Department Head Workflow

Comprehensive HR Leave & Time Off Approval App for Odoo

This Odoo module extends the standard leave (Time Off) approval workflow by introducing an additional approval step for Project Managers and Department Heads before the Team Leader grants final approval. By default, Odoo allows only the Team Leader to approve leave requests. However, if your business process requires that the Project Manager or Department Head must first approve the leave, this module provides the necessary functionality to implement this multi-step approval process.

With this module, a new approval button is added to the Time Off form, allowing the assigned Project Manager or Department Head—configured in the Employee record—to review and approve leave requests before they reach the Team Leader for final approval. This ensures that leave requests are evaluated based on project deadlines, workload distribution, and departmental priorities, helping prevent resource shortages and operational disruptions.

When an employee submits a leave request, the system first identifies the assigned Project Manager or Department Head from the employee’s record. The request then appears for their approval in the Time Off form, where they can review and approve it using the new “Approve” button. Only after their approval does the request proceed to the Team Leader for final validation. If the Project Manager or Department Head does not approve the leave, the request cannot proceed to the next stage.

Main Features:

  • Configure Project Manager / Department Head on Employee Form: Allows assigning a Project Manager or Department Head to each employee. This assigned person will be responsible for approving the employees leave requests before they proceed to the next stage.
  • Configurable Time Off Types for Project Manager / Department Head Approval: Adds a setting on Time Off Types to enable or disable Project Manager / Department Head approval for specific leave types. If enabled, all leave requests under that type must go through Project Manager / Department Head approval first.
  • Works with Odoo’s Standard Validation Options: Integrates seamlessly with Odoo’s existing Time Off Types validation settings:
    1. By Time Off Officer
    2. By Employees Approver
    3. By Employees Approver and Time Off Officer
    Ensures that Project Manager / Department Head approval works on top of these existing validations without modifying standard workflow stages.
  • Prevents Team Leader Approval Without Prior Project Manager / Department Head Approval: If a Team Leader attempts to approve a leave request before the Project Manager / Department Head has approved it, the system raises a warning. This prevents premature approvals and ensures the correct approval sequence is followed.
  • Restricts Team Leader & Time Off Officer Actions Until Approval is Granted: The Team Leader and Time Off Officer cannot approve leave requests until the Project Manager / Department Head has approved first. The system displays a warning message, instructing them to contact the Project Manager / Department Head for approval.
  • Fully Integrated with Odoo’s Time Off Module: Works seamlessly with Odoo’s existing leave request process. No additional workflow stages are added—ensures a smooth and controlled approval process without unnecessary complexity.
  • User-Friendly Notifications & Warnings: The system alerts users when an action is blocked due to missing approvals. This helps employees and managers understand the approval process and compliance requirements.

In this section, we will explain the three validation options that are integrated into this module, along with how the Project Manager / Department Head approval works in each case. These validation options are designed to work seamlessly with Odoo’s standard leave request workflow, ensuring that the Project Manager or Department Head’s approval is considered before proceeding with any further actions.

Flow of "By Time Off Officer" Validation (Validation Set on Time Off Types)

Demo Example:
  • Employee: John Mack
  • Project Manager / Department Head: Johnty Dexter
  • Time Off Officer: Mitchell John
Step-by-Step Workflow for Time Off Request Approval:
  • 1. Employee Makes a Time Off Request
    • John Mack (Employee) submits a Time Off request for a specified number of days (e.g., Vacation).
    • He selects the appropriate Time Off Type (e.g., Vacation) from the available options in the Odoo system.
    • John Mack submits the request for approval.
  • 2. Project Manager / Department Head (Johnty Dexter) Approves the Request
    • Johnty Dexter (Project Manager/Department Head) is identified as the first approver based on the configuration in the system.
    • Once the leave request is submitted, Johnty Dexter receives a notification to review the request.
    • After reviewing the request details, Johnty Dexter has the option to:
      • Approve the leave, or
      • Reject the leave if its not aligned with company policies.
    • If approved, the system will move forward to the next step. If rejected, the leave request is cancelled, and the process ends here.
  • 3. Time Off Officer (Mitchell John) Approves the Request
    • Once Johnty Dexter (Project Manager/Department Head) approves the request, the Time Off Officer (Mitchell John) is notified to review and approve the leave.
    • Mitchell John (Time Off Officer) checks the details of the leave request, including the reason for the leave, dates, and availability.
    • After review, Mitchell John can:
      • Approve the leave, or
      • Reject the leave if there are issues such as insufficient leave balance or other constraints.
    • If approved, the leave is confirmed, and John Mack is granted the requested time off.
    • If rejected, the leave request is denied, and John Mack will be notified of the rejection.

Flow of By Employees Approver (Validation set on Time Off Types)

Demo Examples
  • Employee :- John Mack
  • Project Manager/Department Head :- Johnty Dexter
  • Employees Approver :-Clayton
Steps :
  • Steps for Time Off Request Approval Workflow: Employee (John Mack) submits a Time Off Request. Project Manager/Department Head (Johnty Dexter) reviews and approves the request as the Employees Approver.
  • Employees Approver (Clayton) finalizes the approval of the Time Off Request. This streamlined approval flow ensures that the request is reviewed by the necessary individuals before final approval.

In this validation workflow, both the Employees Approver and the Time Off Officer are required to approve the leave request before it can be finalized. This setup ensures that both the direct supervisor (Employees Approver) and the Time Off Officer review the request, providing a double layer of verification before the leave is granted.

Demo Example: Time Off Request Approval Workflow
  • Employee: John Mack
  • Project Manager/Department Head (Employees Approver): Johnty Dexter
  • Employees Approver: Clayton
  • Time Off Officer: Mitchell John
Steps in the Workflow:
  • Employee (John Mack) submits a Time Off Request for leave.
  • Project Manager/Department Head (Johnty Dexter), who is also the Employees Approver, reviews and approves the leave request.
  • Employees Approver (Clayton) reviews the request and gives the final approval.
  • Time Off Officer (Mitchell John) conducts a final check, ensuring all policies are followed, and approves the request.
  • This sequence ensures that all necessary parties review and approve the Time Off Request before it is finalized, streamlining the approval process and ensuring compliance.

Edition Compatibility:


Enterprise Odoo.sh Community

Streamlining Leave Approvals with Project Manager/Department Head on Employee Form

Time-Off Type Form Enhancement: Include Project Manager/Department Head Approval Checkbox

Enabling Project Manager/Department Head Approval in Employee, Officer, and Dual Validation Workflows

Time-Off Officer Approval Flow for Time Off Types in Odoo

Integrating Project Manager/Department Head Approval with Time Off Officer Options

Employee (John Mack) Makes Leave Request Using Odoo Standard Workflow

Project Manager/Department Head Approval Required Before Time Off Officer Can Approve

Time Off Officer Cannot Click Project Manager/Department Head Approve Button—Only Authorized Approver Can

Department Approval Menu for Leave and Time Off Requests

Project Manager/Department Head (Johnty Dexter) Reviews and Approves Time Off Requests

Time Off Officer (Clayton) Handling Leave Approvals in Odoo Standard Workflow

Managing Time Off Requests: By Employees Approver and Time Off Officer Validation Flow

Integrating Project Manager/Department Head Approval with Employees Approver and Time Off Officer Workflow

Time Off Request Workflow: Employee (John Mack) Requests Leave in Odoo

Department Approval Menu: Managing Leave and Time Off Requests

Time Off Request Validation: Project Manager/Department Head (Johnty Dexter) Approval

Time Off Request Approval: Employees Approver (Clayton) in Odoo Standard Workflow

Employees Approver Approval Triggers "Approve to Second Approval" State Change in Time Off Request

Time Off Request Validation by Time Off Officer (Mitchell John) in Odoo Standard

Time Off Request Approval Flow: Time Off Officer Validation Leads to Final Approval

Contact / Support
Introducing Probuse Consulting Services Pvt. Ltd.

If you need any help or want more additional features, you may contact us through:
Email: contact@probuse.com
Website: www.probuse.com
Skype: mustufa_probuse

Probuse Consulting Service Pvt Ltd is an Software and Web development specialist which offers complete business application together. We are well experienced to provide a face for your business on the software and Internet level.

Probuse Consulting Service Pvt Ltd is a specialist in Odoo/OpenERP services and could give your business open source hand to drive.

Our Services

  • Odoo Implementation

  • Odoo Support

  • Odoo Customization

  • Odoo Migration

  • Odoo Training

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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.