> For the complete documentation index, see [llms.txt](https://docs.facephi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.facephi.com/docs.facephi-en/products/idv-suite/flujos-and-integraciones.md).

# Design and configuration

The [**Flow module**](https://github.com/facephi/facephi-gitbook-docs/tree/master/docs/productos/idv-suite/modulos-manual-de-usuario/flujos-and-integraciones.md) is the starting point for working with IDV Suite.

From this module, product, business, and technology teams can:

* **Design** what the [Onboarding or authentication Flow](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/que-es-un-flujo-de-onboarding-autenticacion.md) (what steps it includes and in what order).
* [**Decide how**](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/integraciones-no-code-low-code.md) that Flow is exposed across the customer's different channels:
  * Integrations **no-code** (hosted experiences, links).
  * Integrations **low-code** (SDK Mobile/web)

All of this is done from a **graphical interface.** The goal is for the client to be able to **evolve their digital identity processes** at the same speed as their business or regulatory needs change.

#### Steps to have an end-to-end Flow in IDV Suite

To implement an Onboarding or authentication Flow in IDV Suite, end to end, the journey is:

1. **Design and configure the Flow in the IDV platform**
   * Access the **Flow module** of IDV Suite.
   * Create a new Flow, choosing whether to start from a template or design from scratch.
   * Configure all capture components (document, biometrics, NFC, etc.) and the functional logic (OCR, Matching, Liveness, morphology, etc.).
2. **Generate the Integration**
   * No-code option. Landing environment.
   * Low-code option (web or mobile).
3. **Configure and publish the Integration**
   1. Adjust specific Integration parameters:
   2. Look & feel (logo, colors).
   3. Subscription to webhooks / callbacks to receive events and results.
   4. Publish the Integration in the corresponding environment and note the **Integration ID** associated with the published Integration.
4. **Integrate the channel (SDK Web / SDK Mobile) using the Integration ID**
   * Low-code:
     * Integrate the SDK Web/Loader or SDK Mobile of IDV Suite into the client's applications.
     * Configure the SDK to run the Flow using the Integration ID obtained after publication.
   * No-code:
     * Backend configuration.
   * In both scenarios, the License that the support team will provide once the Integration is published is required.
5. **Run tests and review the operations on the platform**
   * Perform end-to-end tests from the integrated channel (web or app).
   * Verify that operations are generated correctly and review them from the IDV Suite Operations Module (results, details, possible manual reviews).

#### **Prerequisites**

Before continuing with these steps, the following must have been requested/provided:

* **Client** and **tenant** created.
* **SDK Credentials** configured.
* **Licenses** active for the components that will be used.