> 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/que-es-un-flujo-de-onboarding-autenticacion.md).

# What is an onboarding/authentication flow?

In Facephi IDV Suite, a **flow** is the structured definition of an Identity Verification process.

Simply put:

A flow indicates **what a user has to do**, in **what order**, and **under what rules**, to complete onboarding or authentication.

Each flow consists of:

1. **Asset Capture**\
   These are the actions the user must carry out and the checks the platform performs. For example:
   * Identity document capture.
   * Biometric capture (selfie, liveness check).
   * NFC capture of document data.
   * Fingerprint Capture.
2. **Extractions and validations**\
   Different validation options within the Facephi portfolio:
   * Facial Matching
   * Passive Liveness
   * Document morphology
   * IAD validation
   * OCR extraction
   * Civil registry records

From the client's perspective, the flow is the **basic configuration unit.**

***

#### **Flow types: onboarding vs. authentication**

Although the design mechanics are the same, we distinguish two main types:

* **Onboarding flows**
  * Goal: registering a new user.
  * They usually include Document Capture + biometrics + additional validations.
  * They are normally run only once per user (or at very specific moments: change of country, data update, etc.).
* **Authentication flows**
  * Goal: confirm that the user is who they claim to be before a sensitive action.
  * They can reuse the Biometric Template generated in Onboarding.
  * They are more frequent (recurring access, high-risk operations, account recovery, etc.).

Both types are managed uniformly in IDV Suite, which allows:

* **Reuse components** (capture modules, screens, rules).
* Maintain a **consistent experience** for the user between registration and later access.
* **Simplify** maintenance and governance of the identity model.

***

#### **Lifecycle of a flow**

Every flow in IDV Suite goes through a controlled lifecycle, aligned with the idea of “**design, test, and publish**”:

1. **Create new flow**
   * Select between web or mobile
   * Choose a template or start from scratch
     * Onboarding use case
     * Authentication use case
2. **Design**
   * Once the flow is defined, extra functionality is added if necessary
3. **Flow configuration**
   * Each component of the flow has its own configuration
4. **Save flow**
   1. Name the flow and save it.