> 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/clienten-relaties/objecten-van-clienten.md).

# Objecten van cliënten

Open objecten die aan de huidige cliënt zijn gekoppeld.

## Objecten van de relatie

Gebruik **Objecten van de relatie** om Objecten te inspecteren die aan een Klant zijn gekoppeld.

Dit geeft u context vóór of tijdens het veldwerk.

{% stepper %}
{% step %}

### Open de relatie

Open het klantrecord dat u wilt bekijken.
{% endstep %}

{% step %}

### Open de gekoppelde Objecten

Open de sectie van het Object vanaf het scherm van de Klant.
{% endstep %}

{% step %}

### Ga verder naar het Object

Open het Object dat u nodig hebt voor meer details.
{% endstep %}
{% endstepper %}

### Let op

Beschikbaar zijn de Objecten, afhankelijk van de gegevens van de Klant en de Configureren-instellingen.


---

# 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/clienten-relaties/objecten-van-clienten.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.
