> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bizbone.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Leave Request Business Process
> Configure and customize the workflow used to process Leave Requests.
The **Leave Request** business process defines how leave requests move through the approval workflow from submission to completion.
Administrators can customize this workflow to match their organization's approval requirements, including adding or removing approval levels, configuring decision paths, and automating system actions.
Changes to a business process only apply to new Leave Requests created after the workflow is published. Existing requests continue using the workflow version that was active when they were created.
## Default Workflow
The default Leave Request workflow consists of the following steps:
1. Employee submits a Leave Request.
2. Immediate Supervisor reviews the request.
3. If approved, the request is routed to the L2 Manager.
4. If approved again, the system automatically creates a Work Log.
5. The request is completed.
6. If rejected at any approval stage, the request ends with a **Rejected** status.
### Workflow Steps
| Step | Description |
| ----------------------------------------- | ------------------------------------------------------------------------- |
| **Leave needed** | Employee initiates a Leave Request. |
| **Create request** | Employee completes and submits the request. |
| **Review request (Immediate Supervisor)** | Immediate Supervisor reviews and approves or rejects the request. |
| **Decision** | Routes the workflow based on the approval outcome. |
| **Review request (L2 Manager)** | Secondary approval by the L2 Manager. |
| **Decision** | Determines whether the request proceeds or is rejected. |
| **Create Work Log** | Automatically creates the employee's work log after final approval. |
| **Process completed** | Workflow ends successfully. |
| **Request rejected** | Workflow ends when a reviewer rejects the request. |
| **Request edited** | Request is updated before continuing through the workflow (if permitted). |
### Approval Paths
```mermaid theme={null}
flowchart LR
A[Employee]
--> B[Immediate Supervisor]
--> C[L2 Manager]
--> D[Create Work Log]
--> E([Completed])
classDef complete fill:#16a34a,color:#fff,stroke:#16a34a;
class E compl
```
```mermaid theme={null}
flowchart LR
Employee --> Supervisor
Supervisor --> Rejected
```
```mermaid theme={null}
flowchart LR
Employee --> Supervisor
Supervisor --> Manager
Manager --> Rejected
```
***
## Common Customizations
Administrators can modify the workflow to support their organization's approval process.
### Add Additional Approvers
This example demonstrates how to add an **HR approval** after the **L2 Manager** review.
Navigate to **Administration > Business Process**, then open the **Leave Request** workflow and select **Edit**.
You may need to select and drag other tasks to make space for the new Review Request
Position the new task between **Review Request (L2 Manager)** and **Create Work Log**.
Connect the **Approved** path from the **L2 Manager** decision gateway to the new **Review Request** task. Then connect the new task to the **Create Work Log** task.
This should be done automatically if you positioned the new Review Request in between two steps.
Select the newly added task and configure its properties.
| Field | Example |
| :---------------- | :------------------------------ |
| **Name** | HR Review |
| **Reviewer** | Chosen from Users |
| **Specification** | Users having the following role |
| **Role** | Human Resources Manager |
Configure the approval paths for the new review task.
```text theme={null}
- **Approved** → Create Work Log
- **Rejected** → Request Rejected
```
Select **Publish** to activate the updated workflow.
***
### Remove Approval Levels
Smaller organizations may only require a single approver.
```text theme={null}
Employee
↓
Supervisor
↓
Completed
```
***
### Add Automated Tasks
Automated tasks can be inserted anywhere in the workflow.
Examples include:
* Send email notifications
* Create Work Logs
* Update leave balances
* Notify Payroll
* Generate documents
* Call external systems
***
### Change Decision Paths
Approval and rejection paths can be customized.
For example:
```text theme={null}
Approved → HR Review
Rejected → Return to Employee
```
Instead of ending immediately, rejected requests may:
* Return to the employee for editing
* Allow resubmission
* Notify Human Resources
* Escalate to another approver
***
## Editing the Workflow
To modify the Leave Request workflow:
Open the **Business Process** module.
Locate and open the Leave Request workflow.
Open the workflow designer.
Drag and drop workflow components to:
* Add or remove approval steps
* Change approval routing
* Add automated tasks
* Configure rejection paths
* Modify notifications
Select **Publish** to make the new workflow active.
***
## Workflow Components
The workflow editor supports several component types.
| Component | Purpose |
| -------------------- | --------------------------------------------------- |
| **Start Event** | Begins the workflow. |
| **User Task** | Requires action from a user or approver. |
| **Decision Gateway** | Routes the workflow based on approval or rejection. |
| **Service Task** | Performs an automated system action. |
| **End Event** | Marks completion of the workflow. |
***
## Related Documentation
* [Business Processes Overview](/erp/admin/business-process-overview)
* [Create Leave Request](/erp/requests/leave-request)
* [Leave Request](/erp/timekeeping/leave-request)