> For the complete documentation index, see [llms.txt](https://gitbook.clockin.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.clockin.de/nederlands/begin-met-clockin/einrichtung-fuer-admins/nl-schritt-2-mitarbeiter-anlegen.md).

# Stap 2: Werknemers aanmaken

Zodra je succesvol bent ingelogd om in te klokken, is het nu tijd om medewerkers aan te maken.

Zo werkt het:

1. Open het **werknemersoverzicht** en klik op de blauwe knop **+ Nieuwe werknemer aanmaken**.
2. Voor een snelle start is het voldoende om de **verplichte velden Voornaam en Achternaam** in te vullen. We raden je echter aan om ook **het e-mailadres** in te vullen en het contractuele jaarlijkse verlof in te voeren onder Contractgegevens.

{% hint style="success" %}
☝️ Tip:

Als je in de loop van het jaar begint met inklokken, kun je het beste alleen de resterende vakantie voor het lopende jaar invoeren. Anders zou je met terugwerkende kracht alle afwezigheden van voorgaande maanden moeten invoeren.
{% endhint %}

3. Vergeet niet **op te slaan**!


---

# 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://gitbook.clockin.de/nederlands/begin-met-clockin/einrichtung-fuer-admins/nl-schritt-2-mitarbeiter-anlegen.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.