> 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/attendance-management/attendance-settings.md).

# Attendance Settings

## 1. Function Description 

* In order to facilitate the administrator's operation, it is recommended that the setting sequence for using attendance management for the first time is as follows: \
  Workplace > Punch-in method > Attendance rules > Shift > Attendance group

### **1.1 Attendance Management Assistant**

* This includes a beginner's guide with five tasks. Administrators can click the icon in the lower right corner to pop up the "YOOV Assistant" to view the tasks and their completion status. Once a task is completed, the icon in the lower right corner will disappear.
* For example, the "New User Guide" will lead you through the configuration of attendance group types, attendance times, and locations. After completing the task, clicking on each field will allow you to see the new user configuration items created during the experience.
* To continue with other tasks, click "Add," and the YOOV Assistant will guide you through each configuration step.

<figure><img src="https://3841808194-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FojfjYk9r2Z7NAPxi0WqC%2Fuploads%2F50wFVNIFbhyIAvVvG2th%2Fscreenshot_20250901_153442.png?alt=media&amp;token=fb0ff0a3-a082-4826-ad8d-ffe9440d9d74" alt=""><figcaption></figcaption></figure>


---

# 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/attendance-management/attendance-settings.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.