> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-hr/zh-hk/attendance-management.md).

# 考勤管理

* YOOV 人事管理的考勤管理模組，自動快速計算出員工出勤結果，即時回饋異常結果，確保過程的快捷與準確，考勤APP 讓HR管理更簡單，實現內外勤集中管理，協助企業高效智能的人事考勤管理。

* 大致內容分別為: \
  \- 考勤設置 \
  \- 排班管理 \
  \- 提醒設定\
  \- 每日考勤 \
  \- 當月考勤 \
  \- 考勤報表

* 初次點開考勤管理，自動觸發新手引導

<div align="left"><figure><img src="https://1973974622-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBZneYuSUsErYNDcsI8Fx%2Fuploads%2F35zaQHPmg6IY2pEASlvF%2Fimage.png?alt=media&amp;token=0e146945-369d-4b10-bd97-4f0f3fa41019" alt=""><figcaption></figcaption></figure></div>


---

# 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.coreway.com/coreway-hr/zh-hk/attendance-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.
