Configuration settings

Understanding configuration settings on the first tab of no-code builder

The first tab of the No-Code Builder is where you will find essential settings to customize and configure your workflow.

Configuration settings

The Configuration settings section includes key configurations related to the identification and organization of your workflows. Here’s an overview of the settings you’ll encounter:

Configuration name

• Purpose: The name assigned to the configuration to easily identify it in your dashboard. It must be unique across your company, but it can be changed at any time.

• Tip: Choose a descriptive name that reflects the purpose or specific use of the configuration (e.g., "Standard ID verification flow" or "KYC onboarding"). This makes it easier to locate and manage workflows.

Configuration ID

• Purpose: A unique identifier automatically generated when you create a configuration. This ID is used to reference the configuration in API requests, ensuring that the correct workflow is applied during user verification.

• Tip: Use the Configuration ID in API calls or when linking the configuration to external systems. Keep it handy for integration purposes.

Public URL

• Purpose: The Public URL provides external access to the configured verification flow. This URL is essential for directing users to the verification process, such as through invitation emails, embedded forms, or shared links.

• Tip: Ensure that the Public URL is securely shared with users and is linked to the correct verification process. Only share it with trusted parties and ensure it's used for the intended purpose.

• Activation:

  • The Public URL is disabled by default. You will need to enable it before you can copy and share the link.

  • Refresh button: If you need to change the Public URL permanently, use the Refresh button. This action cannot be undone, so make sure you no longer need the old URL before refreshing it.

  • Temporarily disabling: If you turn off the Public URL, its use will be disabled, but you can enable it again later. This is useful if you need to pause the access without permanently removing the URL.

Default language

• Purpose: Set the default language for the verification flow. This defines the language in which the verification steps, instructions, and notifications will be displayed to the user.

• Tip: Choose the language that best matches the primary user base for this workflow. If you're unsure of the user's preferred language in advance, you can configure a Language step in the Steps tab.

  • In this case, the default language you select here will be pre-selected for the user when they first encounter the language selection step. However, users will still have the option to change it if they prefer a different language.

---

Session settings

The Session Settings section allows you to customize various aspects of the verification session process, controlling how long sessions last, how they can be accessed, and specific verification rules. Here's an overview of the settings you'll encounter:

Session lifetime (minutes)

• Purpose: Defines the maximum duration (in minutes) that a verification session will remain active. After this time, the session will expire, and the user will need to restart the verification process.

• Tip: Specify the session lifetime in minutes based on your security requirements. For example, you might set it to 15 minutes for a quick verification or longer for more detailed processes.

Schedule session

• Purpose: When the Schedule Session toggle is enabled, it allows you to schedule a verification session to take place at a specific date and time in the future. This is especially useful for setting up verification flows in advance, giving users the option to book their session for a later time rather than initiating it immediately.

• Tip: Enable this toggle if you want users to have the flexibility to book their verification session in advance. User-side booking will be handled on your platform, while the session itself can be scheduled on our platform for a designated date and time. This ensures that verification sessions are managed according to your desired timeline and user convenience.

Force user to continue on mobile device

• Purpose: When enabled, this setting forces the user to complete When this setting is enabled, it forces the user to complete the verification process on a mobile device. The session will display a QR code at the beginning, which the user can scan to continue the verification on their mobile device. This ensures that the entire verification process occurs on mobile, which is essential for processes that require mobile-specific features.

• Tip: Enable this toggle if your verification process is designed to be mobile-first or requires mobile-specific features.

Allow user to continue on another device

• Purpose: When enabled, this option allows users to resume their verification process on a different device. This is useful in cases where users start the verification on one device but need to switch to another (e.g., moving from desktop to mobile).

• Tip: Enable this toggle to provide flexibility for users who may need to switch devices without losing progress.

Restrict URL sharing

• Purpose: When enabled, this setting prevents users from sharing the session URL with others. It ensures that only authorized users can access the verification flow and adds an extra layer of security.

• Tip: Use this option if the verification flow contains sensitive or high-security processes that should not be accessible to unintended users.

Screening

• Purpose: Enables or disables screening as part of the verification process. Screening typically involves checking the user’s data against external datasets (e.g., watchlists, sanctions lists) to ensure compliance.

• Tip: Enable this toggle if screening is part of your verification process and you want to ensure users are checked against specific datasets.

• Activation: Screening is available only in paid plans. If you are on a trial plan, it may not function properly. For full access to screening features, you will need to contact our support team to ensure the right permissions are in place.

• Minimum screening score

  • Purpose: The Minimum screening score allows you to set a threshold score that the user must meet in order to pass the screening phase. If the user's screening score falls above this threshold, they will be rejected. This feature helps ensure that only users who meet the required compliance standards proceed in the verification process.

  • Tip: Set this score based on your risk management strategy or compliance standards. For example, if your compliance policy requires a strong match with screening data, you might set the threshold to 85% pass rate.

• Screening Datasets

  • Purpose: The Screening datasets option lets you select which external datasets to use during the verification process. These datasets help verify the user's identity by comparing their data against various lists.

  • Datasets incude:

    • Default

    • UN Sanctions

    • Georgian Sanctions

    • Adverse Media

  • Tip: Choose the relevant datasets based on your industry, regulatory requirements, or business needs. For example, if your organization operates internationally, you may need to use global sanctions lists, while a local business might focus more on national or regional databases.

---

Other settings

The Other Settings section includes additional configuration options to enhance the verification process. Here’s an overview of the settings you’ll find:

Return URL

• Purpose: The Return URL is a custom URL that users are redirected to after completing the verification process. It can be used to direct users to a specific page or action, such as a confirmation page, dashboard, or any other location relevant to your workflow.

• Tip: Define a Return URL to ensure users are redirected seamlessly after the verification process. This is especially useful if you need users to land on a post-verification page (e.g., a success page or next-step instructions).

Pass custom QR URL

• Purpose: If you're using the Force user to continue on mobile device feature, you can provide a custom QR URL. This allows you to pass a unique URL within the QR code that users scan to continue the verification process on their mobile devices.

• Tip: Enable this option if you want the QR code to link to a specific URL. This can be used for special workflows or user-specific data.

Enable SMS notifications

• Purpose: This option allows you to send SMS notifications to users, which can include One-Time Passwords (OTP) or other critical updates related to the verification process. SMS notifications are helpful for user authentication, reminders, and alerts.

• Tip: Enable SMS notifications if your verification process requires real-time communication with users, such as for sending OTPs or session reminders. Make sure to collect user phone numbers as part of the workflow to utilize this feature effectively.

Recurring face recognition

• Purpose: Recurring face recognition utilizes a face database to store facial data from users for future verification sessions. This enhances fraud detection by grouping sessions under a personas feature, allowing you to track users across multiple verification attempts.

• Tip: Enable this feature if you need to track users over time and improve security by detecting repeat users and identifying potential fraud. It is particularly useful for KYC, AML, and other compliance-related processes where recognizing the same user across sessions is crucial.