Use this guide when an existing user cannot sign in, a new account is being created unexpectedly, or a visitor is blocked from creating an account through Social Login, Magic Link, or Email OTP. In many cases, that block is intentional Guardrail behavior designed to keep login forms separate from registration flows.
Start with the account-creation hierarchy
The most common Guardrails confusion comes from checking the individual login method before checking whether the login surface is allowed to create users at all.
- Identify the exact surface: default WordPress login, a supported integration login form, WordPress registration, WooCommerce checkout, or another intentional signup flow.
- For default login forms, check the master Allow new accounts from default login forms setting first. This setting has the highest priority on those surfaces.
- If using Magic Link or Email OTP, then check whether the method is set to Login Only or Login & Register.
- Test once with an email that already belongs to a WordPress user.
- Test separately with an email that has never been used on the site.
- For supported membership/LMS login forms, confirm whether Guardrails are intentionally keeping that login surface existing-user-only and directing new users to the proper registration flow.
A new email cannot create an account
This is not automatically an error. On a login surface that is intended for existing users, blocking account creation is exactly what Guardrails are supposed to do.
A login form is creating new users
If new accounts are appearing from a surface that should authenticate existing users only, check the controls in priority order.
An existing user is not being matched
First confirm that the email being authenticated matches the email stored on the existing WordPress user account.
Do not troubleshoot by creating another user
If the person already has a WordPress account, creating another account can leave the user with separate profiles, memberships, orders, enrollments, or permissions.
First confirm the email address on the original WordPress user. For Social Login, also confirm the provider returns a trusted verified email that matches that account. For Magic Link or Email OTP, test with the existing account email.
Passkey registration looks different
Passkeys follow a separate native account and credential-registration flow. The Guardrail behavior documented for Social Login, Magic Link, and Email OTP does not govern Passkey registration.
A blocked signup on an integration login form may be correct
For supported membership and LMS integrations, VentraConnect Guardrails are designed to keep login forms for existing users from becoming unintended signup forms.
My Account and checkout behave differently
A WooCommerce My Account login can remain an existing-customer surface while checkout remains an intentional account-creation flow. The master/default-login and WooCommerce-specific account-creation controls should not be treated as though every WooCommerce surface has identical behavior. Test My Account and checkout independently with both an existing customer and a brand-new email.
