> 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/support-hilfe/nl-support-login-freischalten.md).

# Hoe activeer ik de supportlogin?

In dit artikel leert u hoe u de supportlogin activeert.

Wat kan ik doen met de supportlogin?\
\
Als je vragen hebt over het inloggen, kun je contact met ons opnemen. Het is vaak handig als we toegang hebben tot je inloggegevens zodat we je het beste kunnen helpen. Dit maakt het voor ons vaak makkelijker om uw probleem te herkennen en snel op te lossen!

Hoe activeer ik de supportlogin?\
\
Volg deze stapsgewijze instructies om de supportlogin te activeren:\
\\

1. Ga via het instellingenwiel naar het menu-item **Accountgegevens**.
2. Selecteer nu **Support Login**.
3. Klik op de blauwe knop **Toegang ontgrendelen**.

\\

{% hint style="info" %}
**Opmerking:** je kunt Support Login ook op elk gewenst moment op deze manier deactiveren.
{% endhint %}

\
Heb je een specifieke vraag of ondersteuning nodig? Maak dan hier een supportticket aan. Ons team helpt je graag!


---

# 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/support-hilfe/nl-support-login-freischalten.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.