# IKO

The IKO module displays integrated customer and object data to case workers and provides a management interface for configuring the presentation.

{% hint style="info" %}
This module requires an active IKO Server installation. The IKO Server is a separate component that retrieves data from backend sources.
{% endhint %}

## What is IKO?

IKO stands for **Integraal Klant- en Objectbeeld**. The purpose of IKO is to provide case workers with a complete overview of the customer or object for which a case is running.

IKO consists of two components:

| Component      | Description                                                                                                                                                                                                                           |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **IKO Server** | A separate application that retrieves data from multiple backend sources to build a complete view. The IKO Server has its own management interface. See the [IKO Server documentation](https://docs.integraal-klant-objectbeeld.nl/). |
| **IKO Client** | Implemented in Valtimo as a module. Displays the aggregated data to the case worker and provides a management interface for configuring the presentation.                                                                             |

<figure><img src="/files/iIgoUs0KchB9NDuNo1GN" alt="IKO detail screen showing customer data"><figcaption><p>IKO detail screen with customer information displayed in widgets.</p></figcaption></figure>

### Data sources

The IKO Server can retrieve data from various backend sources, such as:

* BRP (Basisregistratie Personen).
* KVK (Kamer van Koophandel).
* ZGW APIs (Zaakgericht Werken APIs).
* Domain registrations.

## Why use IKO?

When handling a case, case workers often need information from multiple systems to make informed decisions. Without IKO, they would need to switch between different applications and manually search for related information.

**Example: Processing a benefit application**

A case worker receives an application for special assistance (bijzondere bijstand). To assess the application, they need to verify:

* Personal details and address from BRP.
* Current income and employment status.
* Other running cases for this citizen (e.g., debt assistance, housing support).
* Previous contact moments and notes.

With IKO, all this information is aggregated and displayed on a single screen. The case worker selects the citizen, and immediately sees all relevant data organized in tabs and widgets.

**Other common use cases:**

* **Permit applications**: View property details, previous permits, and enforcement cases for an address.
* **Youth care**: See family composition, school information, and care history for a child.
* **Objections and appeals**: Review the original decision, related cases, and communication history.

## Accessing the IKO view

Case workers can access the IKO view in two ways:

1. **Manual search**: Via the search screen, the case worker can search using the configured search criteria. For example: BSN, surname + date of birth, or address.
2. **Direct link from case**: On the case detail screen, a widget can be configured with a button that opens the IKO view. The identifier (such as BSN or KVK number) is automatically passed from the case document.

{% hint style="info" %}
Configuring a link from a case to an IKO view is done through the case detail tab configuration. See the [Case detail tabs](/features/case/case-detail/tabs.md) documentation.
{% endhint %}

## In this section

| Page                                                                | Description                                                |
| ------------------------------------------------------------------- | ---------------------------------------------------------- |
| [Views](/features/iko/views.md)                                     | Configure IKO Servers and Views.                           |
| [Search actions](/features/iko/search-actions.md)                   | Configure search actions for finding customers or objects. |
| [List](/features/iko/list.md)                                       | Configure search result columns.                           |
| [Tabs](/features/iko/tabs.md)                                       | Organize detail screen information into tabs.              |
| [Widgets](/features/iko/widgets.md)                                 | Configure data display widgets within tabs.                |
| [Search FormIO component](/features/iko/search-formio-component.md) | Embed IKO search and selection in a FormIO task form.      |

## Quick start

1. Navigate to **Admin → IKO**.
2. Add an IKO Server with the server URL.
3. Create a View (e.g. "Customer BRP").
4. Configure Search Actions, List columns, and Tabs with Widgets.

## Related

* [Case detail tabs](/features/case/case-detail/tabs.md)


---

# Agent Instructions: 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:

```
GET https://docs.valtimo.nl/features/iko.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.