> 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/settings/jobs.md).
# Jobs
This feature lets you set up different job roles or tasks that employees can clock in and out of, helping you track labor hours, costs, and productivity by specific job types.
The Jobs tab is where an Admin goes to create a new Job code. To assign rules to the code, they need to then go to the Job Assignment Tab. Time off can be paid, partially paid, or unpaid. Jobs can be paid, partially paid, or not paid.
**To Create a Job Code:**
1. **Add Job** – Opens a form to create a new job with details such as name, code, pay, and project assignment.
2. **Edit / Archive** – Lets you update job details (Edit) or remove jobs from the active list without deleting them (Archive).
3. **Assign Job To User** – Allows you to link or assign specific jobs to selected employees.
4. **Show Archived Jobs** – Displays jobs that have been archived for review or reactivation.
5. **Import Excel** – Lets you upload multiple jobs at once using an Excel file for faster setup.
---
# 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/settings/jobs.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.
