> 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

Set up employee leave calendars, approval workflows, and accrual policies in We360.ai for centralized attendance 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.