# Data Enrichment

The Data Enrichment step allows you to insert one or more configurable pages into the onboarding journey, where users can provide additional structured data and/or upload attachments. When enabled in the Request Type model, an extra step appears during identification to collect this information.

## Direct-hit Goals

* Enable the collection of additional user data during the onboarding process.
* Provide a configurable step within the Request Type model.
* Allow document and attachment uploads within the flow.
* Maintain flexibility to upload non-natively supported documents.
* Automate validation checks with external services.
* Facilitate manual operator review when requests are flagged.


## Pages / Sections / Fields (Admin-configurable)

* Add multiple **pages** and customize the page title & subtitle.
* Within a page, create **sections** (with titles) to group data (e.g., an Address page with sections for 'Residence' vs. 'Domicile').
* Inside each section, add/remove **fields** of various input types.
* Admins can reorder, modify, or delete pages, sections, and fields without code.


## Field Settings

| Setting | Description |
|  --- | --- |
| **Identifier** | String key (e.g., `vat`). |
| **Label** | Human-readable label (e.g., `VAT Number`). |
| **Required** | Yes/No (validation enforced in UI & API). |
| **Editable** | Yes/No (lock values taken from previous steps or providers). |
| **Input type** | text, date, email, phone, dropdown, file, camera, password. |
| **Allowed values/settings** | e.g., regex or option list. Example regex: `^[A-Za-z]{2,4}(?=.{2,12}$)[-_\s0-9]*(?:[a-zA-Z][-_\s0-9]*){0,2}$` |


## Camera Field

Use the device camera to capture a photo of a field. Behavior depends on admin settings and device type.

### Mobile camera **allowed**

* On mobile, the user sees two CTAs: **Take a photo** or **Upload a file**.
* On desktop: the user sees only **Upload a file**.


### Mobile camera **mandatory**

* On mobile: The user sees only **Take a photo**.
* On the desktop, a **QR code** is displayed to switch to a smartphone for capture; the user then continues on the desktop.


## Back Office (Operator UX)

Operators review and edit data provided during Data Enrichment from a dedicated step in the back office.

### Capabilities

* Structured table shows **Page • Section • Field • Key • Value**.
* **The side attachment viewer** remains visible, allowing you to compare entered data with the document content (e.g., a PDF).
* Operators can edit fields under the same **validation rules** (including regex) as end-users.
* Uploaded files can be replaced if permitted; specific fields may require **manual review and approval**.
* If **Doc Processor** ran on an upload, all extracted fields appear; operators can edit values and **approve/reject verifications** (e.g., document type).
* Read-only users see the same data without edit/approval controls.


### Goal

Support the verification and correction of user-entered data to provide error-free data to the integrator.

## Functional Requirements

* **Modification and approval/rejection**: If the request type suspends closure, the operator can modify the data and approve or reject the values.
* **Document comparison**: an always-available viewer enables side-by-side checks of entered data versus the uploaded document.
* **Doc Processor results**: show structured results; allow corrections and validation of checks.


## Example of the Flow

![Data Enrichment](/assets/img_data_enrichment.a3938e4d73780dd46db9262b1ac3e7fafa037d8820af2149b9139a2101a6d359.c6e0f37c.png)