> For the complete documentation index, see [llms.txt](https://documentation.nomos-system.com/nomos-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.nomos-system.com/nomos-system/integrator-nl/eerste-stappen/13.-gebruiksregistratie.md).

# 13. Gebruiksregistratie

In deze stap wordt gevraagd of de controller mag leren hoe de installatie wordt bediend. Daaruit stelt hij later scènes en automatiseringen voor.

Deze stap staat bewust los van de volgende: de hier geregistreerde gegevens blijven op de controller en worden niet naar nomos system gestuurd. De volgende stap gaat over gegevens die wel worden verzonden.

* **Schermweergave:** Er wordt één optie aangeboden:
  * **Registreren hoe apparaten worden gebruikt:** De controller onthoudt welke apparaten wanneer worden bediend. Zonder deze optie wordt niets geregistreerd en ontstaan er geen suggesties.
* **Stap:** Schakel het vakje in of uit naar wens van de klant. De instelling kan later onder Administratie → Geavanceerd worden gewijzigd.
* **Volgende stap:** Klik op "Volgende".


---

# 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://documentation.nomos-system.com/nomos-system/integrator-nl/eerste-stappen/13.-gebruiksregistratie.md?ask=<question>&goal=<endgoal>
```

`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.