> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/outsmart-knowledge-base/outsmart-knowledge-base-nl/mobiele-app/ios-outsmart-app/moduleoverzichten/instellingen/werkperiode-instellingen.md).

# Werkperiode-instellingen

Configureer hoe werkperiodes worden aangemaakt en weergegeven.

## Werkperiode-instellingen

Gebruik **Werkperiode-instellingen** om het gedrag van tijdregistratie te beheren.

Deze instellingen bepalen hoe Uren worden aangemaakt en weergegeven.

### Veelgebruikte opties

* minimale interval
* standaard Skill en standaard Uursoort
* eenvoudige aanmaak van werkperiodes en collega-afhandeling

{% stepper %}
{% step %}

### Open werkperiode-instellingen

Open **Instellingen**, open vervolgens **Instellingen voor werkperiodes**.
{% endstep %}

{% step %}

### Pas de opties aan

Wijzig het interval, de standaardwaarden of de collega-opties die u nodig heeft.
{% endstep %}

{% step %}

### Bekijk het resultaat

Ga terug naar de Uren-flow en controleer of het gedrag past bij uw proces.
{% endstep %}
{% endstepper %}

### Let op

Dit onderdeel kan ook aparte selectievensters openen voor Skill- en Uursoortwaarden.


---

# 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://knowledge.out-smart.com/outsmart-knowledge-base/outsmart-knowledge-base-nl/mobiele-app/ios-outsmart-app/moduleoverzichten/instellingen/werkperiode-instellingen.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.
