> 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/zeiterfassung-1/abwesenheiten/abwesenheitskalender.md). # Absence calendar ## Die Agenturverwaltung calendar view ![](/files/9f284aef1ab9156dbad7e8e52750497d8b3d9144) The calendar view consists of a button (top left) with which a new absence request can be created. Above the calendar we find a paging function that lets us move forward or backward on the timeline to view a different period. The length of the period depends on the size of your browser window. Below the calendar there is an overview of the team's total capacity in hours. This graphic is only visible if the user has the corresponding permission. At the very bottom we find a legend that shows the different possible absence types. ### Representation of different use cases in the calendar ![](/files/14e97b016a933f80c4596a7406726abfa1b1baa9) In this example it is easy to see that the approved and requested absences in calendar week 15 overlap and that at times only one person would be present. ## Request new absence Via the green button at the top left, users — if they have the permission to do so — can make entries in the calendar for themselves and, if they are also authorized, for others. Whether an entry immediately appears as approved in the calendar depends on which absence type was selected and whether that type requires a substitute and/or approval. More on configuring absence types can be found here: {% content-ref url="/pages/8d3870e9a61e5a512d156809596d84a24348e681" %} [Absence types](/die-agenturverwaltung-en/einstellungen-1/absences/abwesenheitstypen.md) {% endcontent-ref %} ### Absences requiring a substitute If an absence type requires a substitute, the requesting user must already select a substitute when submitting the request. ![](/files/ffac060de9f429123ae09c94f877a3ebca7035a0) The substitute then receives a notification and finds a new followup in their followups ... ![](/files/2294ab1c182aa36b1c69963364d952a6b6e76385) ... asking them to either accept or decline the substitution. ![](/files/00320b94e36794a2e95b2815d5b3443d6b4ac7b6) ### Absences requiring approval If the substitute requires approval, after the request a followup is assigned to the persons who are listed as approvers in the absence type. ![](/files/c6f446522f930e5fdd9c4948c7956aa702da2ed5) The assignment for an absence type that requires a substitute only occurs after the substitute has accepted. #### Approval by two people If it is defined in the absence type that approval must be given by a *second* person, the approvers assigned for the second approval receive a followup requesting approval only after the first approval has been granted. ## Deviations from the process ### Assign substitute (instead of requesting) In the calendar an absence can be opened at any time by a suitably authorized person with a click. In the dialog, on the "Substitute" tab a person can simply be selected. The substitute is then simply assigned to that person; they have no option to decline the substitution, but are informed of the assignment via a notification. ![](/files/07b57ae11a2854de39265b5bb68a8417e92464c8) ### Approve absences (even without substitute, first or second approval) In the calendar an absence can be opened at any time by a suitably authorized person with a click. In the "Approval" tab of the dialog an approval can simply be given here — regardless of whether a substitute or first and second approval is required. ![](/files/7635cdd1c98dde4035d747440dc86ccd342e2315) ## Data protection & absence types For employees without the permission *Absences > Calendar > recognize other users' absence types* the reason for absence is not visible to other employees from the calendar. It is only possible to see whether a user is absent or present. Planned (i.e. not yet approved) absences are also shown as hatched here — but without an absence type. For Yvonne in this example, the type is only recognizable by color on her own absences: ![](/files/63a639d05a5f6dcdefbf5f4ecb5a30834aad8625) {% embed url="" %} ## Change or delete absences By clicking on an absence in the calendar a dialog opens that allows me to change the absence type. In the "Delete absence fully or partially" tab I can also either delete the clicked day or the entire absence request. Any existing followups for substitutes or approvals will then also be deleted. ## Subscribe to calendar as iCal You can also subscribe to the absence calendar with your Apple iCal, Google Calendar or Outlook calendar. How to do that is explained here: {% content-ref url="/pages/e7ddef94e30dc90bc52a6ba34bfa5f5edd683b39" %} [iCal integration](/die-agenturverwaltung-en/einstellungen-1/integrationen/ical-integration.md) {% endcontent-ref %} --- # 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/zeiterfassung-1/abwesenheiten/abwesenheitskalender.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.