> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/integrationen/hr-works.md).
# hr works
Similar to Personio, the integration works with the hr works service.
You need an active hr works account for this.
In hr works you then create a new API key for Die Agenturverwaltung. The key requires read permissions for people, general, and absences.
If credentials are stored, absence types are synchronized with hr works. They can then only be edited in hr works. **In Die Agenturverwaltung you still have to set for the absence types whether they should affect time tracking for the hours account and capacity planning.** This can be done under Settings -> Time Tracking -> Absence Types and there for the respective absence type under "Edit". Absence types previously created in Die Agenturverwaltung will be archived.
Die Agenturverwaltung attempts to link users present both here and in hr works based on their email address. If this does not succeed, e.g. because different email addresses are used, you can then manually link hr works UserIds with the users in Die Agenturverwaltung.
For each linked user Die Agenturverwaltung continuously imports all absences from the start date specified here (e.g. 01.01. of the year before last). \
\
\&#xNAN;***Warning: Absences previously created in Die Agenturverwaltung will be deleted in the process.***
If you have questions about the integration, feel free to contact us at
{% embed url="?" %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/integrationen/hr-works.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.