> 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/reference/work-and-time-management/user-interfaces/portal/hr-suite.md).

# HR Suite

We360.ai HR Suite — employee attendance management, break tracking, and leave request workflows.

The HR Suite focuses on core workforce management regarding employee presence and time off.

## Attendance

Detailed logs of employee punch-in and punch-out times, total hours worked, and break durations. Supports filtering by date ranges or individual users.

## Leaves

A dedicated section to manage, approve, or review employee leave requests and balances. Users can view their remaining quotas, while managers have oversight over the entire team's absences.

***

## In This Section

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Attendance</strong></td><td>Punch-in/out logs, hours worked, and break durations.</td><td><a href="https://docs.we360.ai/reference/work-and-time-management/user-interfaces/portal/hr-suite/attendance.md">Attendance</a></td></tr><tr><td><strong>Leaves</strong></td><td>Manage and review leave requests and balances.</td><td><a href="https://docs.we360.ai/reference/work-and-time-management/user-interfaces/portal/hr-suite/leaves.md">Leaves</a></td></tr></tbody></table>


---

# 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/reference/work-and-time-management/user-interfaces/portal/hr-suite.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.
