# Video Selfie The Video Selfie module records a short video of the user performing a guided series of actions, including capturing their ID and selfie, to confirm physical presence and run liveness and face match checks. It can also capture voice consent. For an overview of this module and how it works, see [Video Selfie](https://developer.incode.com/docs/video-selfie). ## Supported With: :white_check_mark: Flows | :white_check_mark: Workflows > **Prerequisites:** Video Selfie requires the ID Capture and Face Capture modules to be completed earlier in the same session. These prior steps provide the reference data used for all downstream comparisons within this module. ## Add Video Selfie to Workflows 1. In the left menu, click **Flow Builder** > **Workflows**. 2. Click **New** or select an existing Workflow. 3. From the Modules list, drag and drop the **Video Selfie** module into the builder. 4. You can click the three dots > **Edit** on the module node to open the [Configuration Options](#configuration-options) panel and adjust settings as needed. > **Note:** In Workflows, Dashboard does not enforce that Face Capture is present before Video Selfie. Adding Video Selfie without a preceding Face Capture step will produce unexpected behavior. Additionally, the **Use as Selfie** setting has a known issue in Workflows that may cause session errors. See the setting description below for details. ### Add Async Resolution Video Selfie is an asynchronous module. It finishes the user interaction quickly, but the final result is not ready immediately. If you run normal branching conditions directly after an asynchronous module, the logic may break. A Process node called Async Resolution prevents this. It instructs the back end to wait for Video Selfie to finish before evaluating conditions and producing a final score or decision. Every branch of your Workflow that includes Video Selfie must include an Async Resolution node before it ends. You can only add conditions after Async Resolution. 1. Open the Workflow where you added the Video Selfie module. 2. From the **Async** list, drag and drop the **Async Resolution** node into the builder. Place it at the end of each branch that includes a Video Selfie module. > **Note:** This is only required for Workflows, not Flows. ## Add Video Selfie to Flows 1. In the left menu, click **Flow Builder** > **Flows**. 2. Click **New** or select an existing Flow. 3. On the **Select Modules** tab, find Video Selfie and click **Add**. 4. You can click **Details & Configurations** to open the [Configuration Options](#configuration-options) panel and adjust settings as needed. > **Note:** In Flows, Dashboard does not allow you to add Video Selfie if you have not previously selected Face Capture. This prevents misconfigured sessions. ## Configuration Options After making changes on any tab, click **Save configurations** to apply them. The settings you see in your configuration options may differ from those documented below. Contact your Incode representative for more information. {/* TODO: Insert screenshot */} ### General | Setting | Description | | ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **_Face Recognition Severity_** | Sets the strictness threshold for the face recognition check. Options: _Low_, _Medium_ (default), _High_. Higher severity requires a closer match between the selfie captured during Video Selfie and the selfie from the prior Face Capture step. | | **_Use as Selfie_** | When enabled, the selfie captured during Video Selfie is used as the Face Capture for the session. This allows Video Selfie to substitute for a separate Face Capture step. **Note:** This option has a known issue in Workflows that causes a session error when no preceding Face Capture step is present. It works correctly in Flows. | | **_Liveness_** | When enabled, runs a real-time liveness check during the selfie capture to confirm the user is physically present and not a spoof or static image. | | **_ID Scan_** | When enabled, prompts the user to show their identity document during the video recording. | | **_Compare ID Enabled_** | When enabled, compares the ID shown during Video Selfie against the ID captured in the earlier ID Capture step to verify it is the same document. | | **_Compare OCR Enabled_** | When enabled, compares the full name extracted via OCR from the ID shown during Video Selfie against the OCR data captured in the earlier ID Capture step. | | **_Tutorials_** | When enabled, displays instructional screens guiding the user through the Video Selfie steps before recording begins. | | **_Allow Video Quality results to affect score_** | When enabled, video quality checks can affect the session score. These checks include whether the video file is present, is non-empty, and contains both video and audio. When disabled (default), these checks are recorded but do not affect scoring. **Note:** This setting is not fully supported in Workflows. Enabling it in a Workflow may not produce the expected score impact. | | **_Seconds_** | The number of seconds at the end of the video to evaluate when **_Execute video quality check for the last seconds of the video_** is enabled. Default: _15_. | | **_Authorization screen_** | When enabled, displays a screen to the user before the video recording begins. {/* Being renamed to "Recording consent screen" in Dashboard UX v2 update */} | | **_Voice Consent_** | When enabled, prompts the user to read a consent statement aloud during the recording. The spoken text is transcribed and validated against the expected statement. When **_Voice Consent_** is enabled, all video quality checks must pass for the Video Selfie score to have a chance of success. | | **_Questions Count_** | The number of questions presented to the user during the Voice Consent step. Default: 3. Only applicable when **_Voice Consent_** is enabled. {/* TODO: Confirm with PM — confirm whether this is the number of spoken consent prompts, and whether it is configurable per client or determined by locale or regulation. */} |