> 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/departments.md).
# Departments
The Departments feature in TimeClockFree lets you organize employees into specific groups or divisions within your company.
This helps you track time, attendance, and reports by department, making it easier to manage payroll, schedules, and labor costs across different areas of your business.
1. **Add Department** – Button to create a new department. Administrators can add a department name and assign employees to it.
2. **Departments List** – Displays all the departments currently set up in the system. Clicking a department shows its details on the right.
3. **Department Name** – Text box to enter or edit the name of the selected department.
4. **Department Members** – Shows the list of employees assigned to the selected department. You can edit this list to add or remove members.
5. **Delete This Department** – Removes the selected department from the system permanently.
---
# 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/departments.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.
