> 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/leave-categories.md).
# Leave Categories
Leave Categories in TimeClockFree let you create and manage different types of leave (such as vacation, sick leave, or personal days).
Administrators can define each leave category so employees can request and track time off accurately. This feature helps keep leave records organized and ensures proper reporting of paid or unpaid leave.
1. **Add Category** – Button to create a new leave category (e.g., Vacation, Sick Leave).
2. **Category List** – Displays all existing leave categories for selection and editing.
3. **Category Name** – Field to enter or edit the name of the leave category.
4. **Calculations (Paid/Unpaid)** – Dropdown to choose whether the leave category is paid or unpaid.
5. **Status (Active/Inactive)** – Dropdown to set whether the leave category is currently active or inactive.
6. **Delete this Category** – Removes the selected leave category 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/leave-categories.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.
