> 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/blog2/readme.md).

# Welcome to the Open Time Clock Blog

This is the official blog and update hub for Open Time Clock. We share product deep dives, best practices, release notes, tips, and real customer stories to help you manage time tracking and scheduling more efficiently.

What you’ll find

* Release notes: What’s new, improved, and fixed.
* How‑to guides and tips: From first steps to advanced configuration.
* Case studies and insights: How different industries succeed with Open Time Clock.
* FAQs and troubleshooting: Practical answers to common issues.

Get started

* New to Open Time Clock: Your first‑time setup guide
* Feature overview: Time clock, scheduling, leave, and reporting
* Integrations: Connect with popular payroll and HR systems
* Security and compliance: Data protection, permissions, and audit

Need help?

* Contact support or submit a ticket
* Join the community for shared best practices
* Browse the full documentation

Note\
Follow this page to get the latest updates—we publish feature breakdowns and actionable recommendations as soon as they go live.

If you want a more marketing, technical, or bilingual tone, tell me your audience and style preferences, and I’ll tailor it.

### Jump right in

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-bolt">:bolt:</i></h4></td><td><strong>Quickstart</strong></td><td>Create your first site</td><td></td><td></td><td><a href="broken://pages/7FvWQMF0kTK7HGhlQfmo">Broken link</a></td></tr><tr><td><h4><i class="fa-leaf">:leaf:</i></h4></td><td><strong>Editor basics</strong></td><td>Learn the basics of GitBook</td><td></td><td></td><td><a href="https://github.com/GitbookIO/gitbook-templates/blob/main/product-docs/broken-reference/README.md">https://github.com/GitbookIO/gitbook-templates/blob/main/product-docs/broken-reference/README.md</a></td></tr><tr><td><h4><i class="fa-globe-pointer">:globe-pointer:</i></h4></td><td><strong>Publish your docs</strong></td><td>Share your docs online</td><td></td><td></td><td><a href="broken://pages/QPzbTvC6XsT5gERiU43E">Broken link</a></td></tr></tbody></table>


---

# 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/blog2/readme.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.