Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

    English (US)
    MX Spanish (Mexico)
    CA French (Canada)
    US English (US)
    • Home
    • Management Tools
    • Security

    User multi-factor authentication (MFA)

    Written by Lindsey Stanifer

    Updated at August 20th, 2026

    Contact Us

    If you still have questions or prefer to get help directly from an agent, please submit a request.
    We’ll get back to you as soon as possible.

    Please fill out the contact form below and we will reply as soon as possible.

    • Getting Started
      Setting up your calendar Managing your alerts Additional Settings
    • Daily Processes
      Candidate Inbox Candidate Profile My Calendar/Calendars Browser Extension My Jobs Approvals Engine Manual and Common Scheduling Practices Form I-9 processes Troubleshooting Forms & Offers
    • Candidate and User Engagement
      Campaigns Conversation Builder Surveys Channels Talent Community Voice Web Management Analytics & Reporting Data Privacy Career Sites
    • Management Tools
      Job Management Scheduling Security Journeys Content Management System (CMS) Multiple Brands Workflows Users, Roles and Permissions Data Feeds Location Management Lookup Tables Assistant Messaging Company Information Client Setup System Attributes Integration Center
    • Contextual AI
      Knowledge Training Library
    • Conversational Events and Campus
      Conversational Events Campus Events
    • Employee Communications
      Communications App Employee Management
    • Release Notes
      2025 2026
    • Workday Feature Descriptions
    + More

    Table of Contents

    Users not impacted Two-factor authentication logic User experience Verification code SMS autofill Troubleshooting tips

    As of Aug 4, 2025, all accounts without SSO or two-factor authentication (2FA) already enabled will have 2FA enabled for their accounts. This adds an additional layer of protection for all accounts.

    While two-factor authentication (2FA) will be the minimum standard for account security, Single Sign-On (SSO) is our recommended account access setup, if available.  

     

    Users not impacted

    All accounts except the following will be impacted:

    • Basic/Limited users
    • Users that sign in via SSO

    Two-factor authentication logic

    After this feature is auto-enabled, the following logic will apply to your account:

    • The contact method used for two-factor authentication will be email address. The email address stored on each user's profile will be used to send authentication emails to the user.
    • The password reset interval will be set to 90 Days. This ensures that your team members reset their passwords regularly.
    • Users will remain logged in 8 hours (if previously undetermined) after they are inactive in the CEM. After this timeframe, the user will be logged out of the system and must re-authenticate themselves by logging in with their email address and password.

    For accounts created after August 4, 2025, the above settings will be the default selections if you are not utilizing Single Sign-On (SSO).

     

    User experience

    The first time that a user logs in with a username and password on or after August 4, 2025, they will then receive a one-time passcode via the email associated with their user account, which they will then use to authenticate their account login.

    After this initial authentication, a user will need to log in to the system each time they reach the end of their inactive session (default of 8 hours).

    Verification code SMS autofill

    When completing 2FA on a supported mobile device (iOS or Android), users can use the automated keyboard suggestion to instantly enter their verification code. This feature is available across the Paradox Native App and all Paradox web pages.


    Troubleshooting tips

    If your users are not receiving verification codes for MFA, then it most likely is due to one of the below reasons:

    • User is unsubscribed.
    • User has filtered olivia.alerts@paradox.ai emails and can’t find them in their inbox.

    After checking the above scenarios, we encourage you to contact your CS Representative for further troubleshooting.

    account mfa account 2fa multi-factor authentication authenticator log in key code phone number sign on verification conversational ats integrated ats

    Was this article helpful?

    Yes
    No
    Give feedback about this article

    Related Articles

    • System verification for both candidates and users
    • Spam and blacklisting
    • Referral phone numbers
    • Single Sign On (SSO)

    Copyright 2026 – Paradox.

    Knowledge Base Software powered by Helpjuice

    Expand