This article gives a decision framework for selecting standard vs emailcheck login mode based on your audience, security posture and SSO usage.
Decision Factors
- Do you use external IdPs (SSO)? If yes, emailcheck is strongly preferred — it lets the platform route users to their identity provider automatically.
- Are usernames public-facing? If anyone can guess valid emails (e.g. employee names), emailcheck reduces enumeration risk.
- Does your audience use password managers? Mostly fine with both; some legacy managers handle standard better.
- Do you have a single auth method? If everyone uses local username/password, standard is simpler.
Common Configurations
- SaaS with corporate SSO: Emailcheck. The platform detects whether the email's domain has an SSO config and redirects accordingly.
- Healthcare clinic: Emailcheck. Patients see a password field, clinicians get redirected to Microsoft.
- Small business app: Standard. Everyone has a single password-based account; simplicity wins.
- Public consumer site: Standard. Friction matters most; emailcheck adds a step.
Switching Modes
You can change the mode at any time without re-issuing credentials. Existing users notice the new flow on their next sign-in. Provide a brief banner explaining the change.
Tip: Test the chosen mode with a few users before global rollout. Edge cases (password managers, screen readers, single-page-app deep links to the login page) often surface only in real usage.