> For the complete documentation index, see [llms.txt](https://www.opentimeclock.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opentimeclock.com/docs/product-q3/settings/clock-groups.md).
# Clock Groups
This feature allows you to organize employees into specific groups for time tracking purposes.
It helps manage and monitor clock-in/clock-out activities by department, location, or job type, making it easier to apply settings, schedules, and reports to multiple employees at once.
1. **Add Clock Group** – Lets you create a new clock group to organize employees under a specific interface or location.
2. **Clock Groups List** – Displays all existing clock groups so you can select and manage them individually.
3. **Settings Tab** – Opens configuration options for the selected clock group, such as name, interface, and security.
4. **Group Name** – Field where you define or edit the name of the clock group.
5. **Interface Dropdown** – Allows you to select the type of clock-in method for this group (e.g., IO Board Clock, Scan & Tap Clock, PIN Clock, or Name Clock).
6. **Security Option** – Lets you enable a password requirement for employees to access this clock group.
7. **Create Group Password** – Allows you to set or update the password if security is enabled.
8. **Display Settings** – Choose how to view clock-in/out lists (one list or two separate lists) for the group.
9. **Columns Options** – Checkboxes to show or hide activity/status, date, time, elapsed time, and new message count on the group display.
10. **Delete This Group** – Removes the selected clock group permanently from the system.
---
# 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://www.opentimeclock.com/docs/product-q3/settings/clock-groups.md?ask=&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.
