No, by default, MFA is not enforced for users, and they are not prompted to set up MFA during login.
When specifically configured, only users logging in with Email & Password will be prompted to set up and complete MFA.
Yes, admins can configure various MFA options, such as requiring MFA every login, remembering for 7 or 30 days on known devices. Users will see these options during setup.
Yes, device fingerprints are generated on the first login, saved, and associated with user accounts for MFA validation.
Yes, changing the browser will prompt Multi-factor Authentication, regardless of the selected 7-day or 30-day frequency.
Removing cookies will trigger MFA, independent of the chosen frequency setting.
Yes, existing users will be prompted to set up MFA on their next login if MFA requirements are added.
When multiple users log in from one browser, each user maintains their own MFA validation settings, unaffected by other users’ settings, even in mixed modes of browsing.
Yes, users can configure MFA settings for their accounts, which are validated during login.
Users' MFA configurations will be updated according to the organization settings. Users will default to the minimum available option if a previously selected option is removed.
Users will be prompted for MFA verification after the session timeout, even if they have a valid MFA memory time.
Users will be prompted for MFA verification before the session timeout occurs.
Users will be prompted for MFA verification exactly at the session timeout.
Users will be prompted for MFA verification every time they log in.
Yes, an admin can reset MFA for a user, requiring them to set up MFA again on the next login.
Yes, an admin can disable MFA for a user, allowing new users to log in without MFA. Existing users will still be prompted for 2FA.
MFA should work seamlessly across different mobile devices and browsers.