• Product

    Document Studio

    Generate, Sign, and Automate Salesforce documents with real-time sync

    Document Generation
    eSign
    Files
    CLM

    Experience Studio

    Build portals, apps, and forms directly in Salesforce with Dynamic data flow and adaptability

    Forms
    Flows
    Portals
    Surveys

    Go Unlimited

    Portals & Web Apps
    High-Volume Doc Gen
    Forms & Synced Surveys
    eSign & Contract Lifecycle
    Enterprise Compliance
    All-in-One Suite
    Book a demo
  • Solutions
    Financial Services
    eCommerce
    Legal
    Tech
    Insurance
    Nonprofit
    Manufacturing
    Education
    Healthcare
Log In Slack sales

Titan Support

How can we help you?

Platform

SmartV: Configure Authentication and Two-Factor Verification

What Is SmartV Authentication?

SmartV Authentication controls how users verify their identity before accessing a Titan Web project.

When two-factor authentication is enabled, users must complete an additional security check after meeting the SmartV login and condition requirements. They can enter a verification code on the SmartV Verification page or open a one-time quick link, depending on how you configure the project.

The Verification page uses the SmartV OTP Form widget to collect the user’s code. You can configure this widget to control the accepted code format and how the form behaves after an incorrect entry.

When to Use Two-Factor Authentication

Keep two-factor authentication enabled for live projects that display protected information or let users update Salesforce data.

You can temporarily disable it while building and testing the project. This lets you test the login and condition settings without repeatedly checking your email for a new verification code.

When 2FA is disabled, any user who meets the configured login and condition criteria can access the project without completing another verification step.

How SmartV Two-Factor Authentication Works

When a user attempts to sign in:

  1. Titan checks the login information against the configured Salesforce object.
  2. Titan confirms that the matching record meets the SmartV conditions.
  3. Titan generates a verification code and temporarily stores it in the selected Salesforce field.
  4. Titan or Salesforce sends the code to the user.
  5. The user enters the code in the SmartV OTP Form.
  6. Titan compares the entered code with the value stored in Salesforce.
  7. If the values match, the user can access the project.

You can also generate a SmartV quick link. This allows the user to complete verification by opening a one-time URL instead of manually entering the code.

Before You Begin

Make sure you have:

  • Configured the SmartV Login settings.
  • Configured any required SmartV Conditions.
  • Access to the Salesforce object selected during the Login step.
  • A dedicated Salesforce number field that can store at least six digits.
  • Permission to configure the project’s email settings.
  • A Salesforce text field that can store at least 300 characters if you plan to generate a SmartV quick link.

The verification code field can have any name. Using a clear name, such as SmartV Verification Code, makes its purpose easier for Salesforce administrators to identify.

Configure Two-Factor Authentication

  1. In the Authentication step of the SmartV wizard, enable Two-Factor Authentication.
    Keeping this option enabled is recommended for live projects because it requires users to confirm their identity after passing the initial login checks.

    You can turn it off temporarily while testing. When it is off, users who meet the Login and Condition criteria can access the project without entering a verification code.
Turn on the recommended Two-Factor Authentication option in the SmartV Authentication settings.
Enable two-factor authentication during the Authentication step of the SmartV wizard
  1. From the Verification Code Field drop-down list, select the Salesforce field where Titan should temporarily store the generated login code.
    The selected field must:
    • Belongs to the Salesforce object selected during the Login step.
    • Be a number field.
    • Support a code containing at least six digits.
    • Be dedicated to storing the SmartV verification code.
  2. Titan compares the user-entered code with the value stored in this field. The user can access the project only when the values match.
Select a verification code field in the SmartV wizard and view the corresponding field on a Salesforce contact record.
Select the Salesforce field that will temporarily store the SmartV verification code

Configure the Verification Email

  1. Turn on Send email with code to user if you want the verification code sent automatically.
  2. Choose your preferred method for sending the verification email by selecting the Salesforce or Titan radio button:
    • Salesforce: Sends the email through your Salesforce organization. This is the recommended option and can use an organization-wide email address.
    • Titan: Sends the email through the Titan mail server. You can use this as a fallback when Salesforce email is not configured.
Configure Salesforce or Titan to send the verification code and enable the Verification page for all login attempts.
Choose the mail server and decide when Titan should display the Verification page
  1. If you select Salesforce, select the Gear icon to open the Salesforce email settings.
  2. From the Org Email drop-down list, select the Salesforce organization-wide email address that should send the verification code.
    Using an approved organization-wide address helps users recognize the sender and keeps authentication emails consistent with your company communications.
  3. Select Use Titan mail server as fallback if Titan should attempt to send the email when it cannot be sent through Salesforce.
  4. Select Apply to save the email configuration and return to the Authentication screen.
Configure send email via Salesforce window with an Org Email selected, the Titan mail server fallback enabled, and an Apply button
Select the Salesforce organization-wide email address and configure the Titan mail server as a fallback

A SmartV quick link lets the user verify their identity by opening a one-time URL. This removes the need to copy the verification code from an email and enter it manually.

The link is valid for one session. After it has been used, it expires and cannot be used again.

  1. Turn on Generate SmartV Quick Link.
  2. From the Store Link Field drop-down list, select the Salesforce field where Titan should save the generated URL.
    The selected field must support at least 300 characters. A rich-text or long-text field can be used if it meets this requirement.
  3. Turn on Hide SmartV OTP Form if users will verify themselves only through the quick link.
    When this option is enabled, the Verification page does not display the fields for entering a code. Instead, users are instructed to open the URL sent to them.
    Leave the option turned off if users should still be able to enter a verification code on the page.
Enable the SmartV Quick Link, select a Salesforce field for the URL, and configure the Hide SmartV OTP Form option.
Generate a SmartV quick link, select its Salesforce storage field, and choose whether to hide the OTP form
  1. Configure Salesforce automation to send the link to the user after Titan populates the selected field.

The user sees the following message when the OTP form is hidden:

Verification page instructing the user to log in through the URL provided by email, with an option to resend the link.
The Verification page directs the user to the quick link sent by email

Configure Google Sign-In

Google sign-in provides another authentication option for users with a Google account.

  1. Turn on Sign In Using Google.
  2. From the Google Identity Field in Salesforce drop-down list, select the Salesforce field that associates the user’s Google identity with their Salesforce record.
  3. Enter the Google Client ID for your Google application.
  4. Enable the Google People API for the applicable Google Cloud project.
Google sign-in settings showing the Salesforce identity field and Google Client ID options.
Connect SmartV authentication to a Google identity field and Google Client ID
  1. Select Next to continue to the SmartV Profile settings.

Configure the SmartV OTP Form

When 2FA is enabled, and the OTP form is displayed, users enter their verification code on the Verification page.

SmartV Verification page with six code fields, a Log In button, and a Resend the Code link.
Users enter the code sent to their verification address on the SmartV Verification page

You can use the SmartV OTP Form widget to configure the Verification page or create a custom verification experience.

Note: The SmartV OTP Form requires Apex in Salesforce. Contact Titan Support for help with the required implementation.

Add the SmartV OTP Form Widget

  1. Open the page where users will enter their verification code.
  2. Select the + icon to open the Elements panel.
  3. Select Widget.
  4. Add the SmartV OTP Form widget to the page.
SmartV OTP Form widget highlighted in the Widget section of the Titan Web Elements panel.
Add the SmartV OTP Form widget from the Elements panel
  1. Select the widget, and then select the Gear icon to open the SmartV OTP Form Settings.

Configure the Code Format

  1. Under Content, configure the values that users may enter:
    • Allow numbers: Allows numerical values.
    • Allow text: Allows letters.
    • Allow numbers and Allow text: Allows alphanumeric values.
  2. Use the Number of characters to set the required length of the verification code.
    This value should match the code generated by your Salesforce implementation. For a standard six-digit code, enter 6.
SmartV OTP Form Content settings with numbers allowed and the number of characters set to six.
Set the accepted characters and the required length of the verification code

Configure the Widget Display

  1. Select the Hide button if another element or action will submit the verification code, and you do not want to display the widget’s Log In button.
  2. Select Hide Onload if the OTP form should be hidden when the page first opens.
    You can display the form later using a condition or action when the user reaches the verification stage.
Hide button and Hide Onload options in the SmartV OTP Form Content settings.
Hide the OTP login button or the complete widget when the page loads

Clear an Incorrect Code

  1. Open the Interactivity settings.
  2. Select Clear warning on re-enter.

When a user enters an incorrect code, the widget displays a warning. This option clears the warning and the previous values as soon as the user starts entering a new code.

Enable Clear warning on re-enter in the SmartV OTP Form Interactivity settings.
Clear the warning and previous values when the user enters a new code

Test the Authentication Process

Test the complete login process before publishing the project.

Confirm that:

  • A user who meets the Login and Condition criteria can continue to verification.
  • Titan or Salesforce sends the verification email.
  • The email is sent from the expected address.
  • The Salesforce field receives the generated code.
  • The OTP form accepts the configured number of characters.
  • A correct code grants access.
  • An incorrect code prevents access.
  • The warning clears when the user enters a new code.
  • The quick link works once and cannot be reused.
  • The OTP form is hidden when Hide SmartV OTP Form is enabled.
  • Google sign-in matches the correct Salesforce record.

You can temporarily disable 2FA while checking the Login and Condition settings. Turn it back on and complete at least one full verification test before publishing the project.

Frequently Asked Questions

Is Two-Factor Authentication Required for SmartV?

No. Users can access the project without an additional security check when 2FA is disabled, provided they meet the configured Login and Condition criteria.

Keeping 2FA enabled is recommended for live projects.

Can I Disable 2FA While Testing?

Yes. Disabling 2FA can speed up testing because you do not need to retrieve and enter a new code for every login attempt.

Remember to enable it again and test the full authentication process before publishing.

What Type of Salesforce Field Should Store the Verification Code?

Use a dedicated number field on the Salesforce object selected during the SmartV Login setup. The field can have any name, but must support at least six digits.

Why Is the Verification Code Stored in Salesforce?

Titan temporarily stores the generated code in Salesforce so it can compare that value with the code entered by the user. Access is granted only when the values match.

Should I Use Salesforce or Titan to Send the Code?

Salesforce is the recommended mail server. It lets you send the email through your Salesforce organization and use options such as an organization-wide email address.

The Titan mail server can be used as a fallback.

A verification code must be entered in the SmartV OTP Form. A quick link lets the user complete verification by opening a one-time URL.

No. The link is valid for one session and expires after use.

Enable Hide SmartV OTP Form if users should verify themselves only through the link. Leave it disabled if you still want users to enter a verification code on the page.

Can the OTP Form Accept Letters and Numbers?

Yes. Enable both Allow numbers and Allow text to accept an alphanumeric code. The settings must match the code created by your Salesforce implementation.

On this page

The Only Forms Solution Built 100% in Salesforce.

Slack an expert