Table of Contents
Introduction
Why FluentCRM itself does not handle two-factor login
If 2FA isn’t prompting, FluentCRM isn’t protecting anything — you’ve got email access with single‑factor risk. This usually comes down to caching, custom login redirects, role rules, plugin conflicts, or 2FA settings being off. Here’s how to diagnose fast and apply the fixes that actually stick.
What a missing prompt puts at risk
Without a prompt, one stolen password can expose your contact lists and campaigns.
Enforce 2FA for the Right User Roles in Your WordPress 2FA Plugin
Start with the plugin that actually shows the login prompt. If it does not apply to your user’s role, no prompt appears.
Role-based enforcement settings
Open your 2FA plugin settings in WordPress and check which roles are required to use two-factor login.
- Confirm the role of the user who is not being prompted.
- Include the roles your team uses to manage FluentCRM.
- Save the settings and log in again with a test account.
The FluentCRM CRM Managers screen controls plugin access, not login rules.
Grace periods that delay the prompt
Many 2FA plugins give users a grace period before setup becomes mandatory. During that window, the prompt may stay hidden.
Shorten the grace period or end it, then test again with a fresh session.
Fix Code Delivery with an SMTP Plugin like WP Mail SMTP
Why emailed codes never arrive
If your 2FA plugin sends codes by email, delivery matters. WordPress is not designed to send emails, and wp_mail() typically relies on the default PHP mail() function of your web server.
That setup often fails. A “From” address that does not match your domain can also cause delivery problems.
An SMTP plugin like WP Mail SMTP connects WordPress to a proper mailer service.
Testing with email logging
Turn on email logging after you connect the mailer.
- Log in with a test account.
- Check the log for the code email.
- Resend any failed message.
If the email appears in the log but not the inbox, check the spam folder and your sender settings.
Resolve Plugin Conflicts by Isolating FluentCRM and Your 2FA Plugin
If roles and email delivery check out, another plugin may be blocking the prompt.
Deactivate and retest method
FluentCRM’s troubleshooting guidance suggests a simple isolation test. Deactivate all plugins except FluentCRM, FluentCRM Pro, and your 2FA plugin, then retest.
- Deactivate the other plugins.
- Reactivate plugins one at a time until the prompt disappears.
The last plugin you turned on is the likely cause.
Security plugins that override each other
Two plugins that both control login screens can clash. One may skip or replace the other’s prompt.
Keep a single plugin in charge of two-factor login. Disable the duplicate feature in the other one, then test again.
FAQ
Does FluentCRM have built-in two-factor authentication?
No. FluentCRM handles contacts and email marketing. Login prompts come from WordPress and your 2FA plugin.
Why does one user get a prompt while another does not?
Role-based enforcement is the usual cause. The second user’s role may not be required, or a grace period may still be active.
Can FluentCRM Pro cause the missing prompt?
Rarely. Run the isolation test with only FluentCRM, FluentCRM Pro, and your 2FA plugin active.
Conclusion
A missing 2FA prompt almost always traces back to three places: role enforcement, code delivery, or plugin conflicts. Work through them in that order.
