> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/how-to-and-best-practices/mastering-time-and-attendance/global-leave-management.md).

# Global Leave Management

We360.ai provides a centralized leave management system — configure leave types, approval workflows, and leave calendars for your entire organization.

## Setup Steps

{% stepper %}
{% step %}

#### Define Leave Types

Go to **Settings → Workplace → Leave Types** and create the leave categories your organization uses (e.g., Annual Leave, Sick Leave, Compensatory Off). Set the accrual rate and maximum balance for each type.
{% endstep %}

{% step %}

#### Create a Holiday Calendar

Under **Settings → Workplace → Calendars**, set up your organization's national and regional holiday calendar. Assign the calendar to the relevant teams or locations.
{% endstep %}

{% step %}

#### Configure Approval Workflows

Define who approves leave requests. By default, a user's assigned manager is the approver. You can configure secondary approvers or auto-approval rules for short-duration leave.
{% endstep %}

{% step %}

#### Employees Submit & Managers Approve

Employees submit leave requests from the **HR Suite → Leaves** page. Managers receive a notification and can approve or reject requests directly from the portal.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Approved leaves are automatically reflected in the employee's attendance report, ensuring accurate timesheets.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.we360.ai/how-to-and-best-practices/mastering-time-and-attendance/global-leave-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.