Skip to content

Require MFA and track enrollment

AtmanID has no “enrollment campaign” object. You drive enrollment with three controls: a per-role requirement (with a grace period), the User Compliance view of who is enrolled, and the reminder users see until they enroll. All of it is on Platform Config → Authentication → MFA (the MFA Management page).

Who can do what

Task Roles
Open MFA Management Identity Admin, Tenant Owner, Security Analyst, PAM Admin, CISO, Super Admin
Edit policies and exception rules PAM Admin, Tenant Owner, Super Admin
Reset a user’s MFA Identity Admin, Tenant Owner, Super Admin

Factors users can enroll

  • Authenticator App (TOTP): one per user, six-digit codes.
  • Passkey (WebAuthn): Touch ID, Windows Hello or a security key. A user can register several.
  • Backup Codes: one-time recovery codes, issued when a user enrolls and regenerated from their MFA page.

SMS, email codes, push and voice are not supported.

Require MFA for a role

  1. Open the Enforcement Policies tab. Each role shows whether it uses Your organisation settings or the Platform default, and an Adoption bar (enrolled / total).
  2. Click Edit on the role.
  3. Tick Require MFA for this role.
  4. Set the Enrollment Grace Period (0–90 days). At 0, users without MFA are blocked at their next login. The grace clock starts when you switch the requirement on; editing other fields later does not restart it. Users who already have a factor get no grace: they are challenged at their next sign-in.
  5. Optionally set Minimum Authenticator Strength to Phishing-resistant only. Only passkeys are then accepted; TOTP and backup codes are rejected at login after the Phishing-Resistant Grace Period (0–90 days).
  6. Check the Pending Changes preview and click Save Policy.

For Super Admin, PAM Admin, Identity Admin and CISO you can only make the policy stricter than the platform default; a weaker setting is rejected. Reset to default removes your organisation’s override for that role.

Allowed Factors limits which factors a role may sign in with (Authenticator App, Passkey, Backup Codes). It is checked at every sign-in. While enforcement is in its warn phase, a sign-in with a factor outside the list still succeeds and is recorded in the audit trail as MFA_FACTOR_NOT_ALLOWED (outcome would_block); once enforcement is switched on, it is refused and the user is told which factors they can use. Check those audit events before you remove a factor that people are still signing in with.

What a user who has not enrolled experiences

  • While a grace period runs, they can work normally. End users also see a banner on their dashboard, Multi-factor authentication is not set up on your account, with a Set up MFA button.
  • Once the grace period ends (or immediately, with no grace), every page except their profile redirects to Multi-Factor Authentication (/dashboard/profile/mfa) until they enroll.
  • Enrolling: Set up authenticator app, scan the QR code, enter the 6-digit code, Confirm & activate MFA, then save the backup codes. Passkeys are added under Passkeys (Phishing-Resistant) → Add a passkey.
  • A user whose role requires MFA cannot remove their last factor.

Track who has enrolled

On the User Compliance tab, the stat cards (Total Users, Enrolled, MFA Required, Non-Compliant) filter the table when clicked. The filter pills are All, Enrolled, MFA Required, Compliant, Non-Compliant, Optional, Exempt. Non-Compliant is your follow-up list: required but not enrolled.

You can also filter Identity & Access → Directory by MFA enrollment (Enrolled / Not enrolled).

There is no export, scheduled MFA report or reminder email to non-enrolled users. Follow up through your own channels using the Non-Compliant list.

Require MFA for one user, or on risky sign-ins

  • One user: on Security & Risk → Risk & Intelligence, the Require MFA row action requires MFA for that user whatever their role’s policy. On User Compliance their Required? column then reads Required for This User; Clear next to it removes the per-user requirement, and their role’s policy applies again from their next sign-in. Identity Admin, Tenant Owner and Super Admin can set and clear it. Both are recorded in the audit trail (INTELLIGENCE_MFA_ENFORCEMENT_REQUESTED, INTELLIGENCE_MFA_ENFORCEMENT_CLEARED).
  • Risky sign-ins: Authentication → Risk-based auth → Policy has an MFA Required Threshold. Logins scoring above it must pass MFA.

Exceptions

The Exceptions tab holds rules by Email pattern (LIKE) or Individual user (UUID). Every rule needs an Expires date, at most 365 days ahead. Until then, a matching user is shown as Exempt on User Compliance and their role’s MFA requirement is lifted at sign-in. An exception never covers:

  • the Super Admin, PAM Admin, Identity Admin or CISO roles;
  • a user who has an individual Require MFA (see above);
  • a sign-in the risk engine scores as high-risk.

Each sign-in a rule covers is recorded as MFA_EXEMPTION_APPLIED. While exemptions are in their warn phase, the user is still asked for MFA and the event’s outcome is would_exempt; once exemptions are switched on, it is exempted.

Rules created before expiry dates were required show No Expiry — Report Only. They do not apply at sign-in and do not make anyone Exempt; remove them and add a rule with an expiry date.

Reset a user’s MFA

On User Compliance, click Reset MFA on the user’s row and confirm. All their TOTP and passkey factors are removed, they receive an in-app notification, and they set up MFA again at next sign-in. You cannot reset your own MFA, and your own session must have passed MFA.

Audit trail

Look for MFA_POLICY_UPDATED, MFA_POLICY_OVERRIDE_REMOVED, MFA_FACTOR_NOT_ALLOWED, MFA_EXCEPTION_CREATED, MFA_EXCEPTION_DELETED, MFA_EXEMPTION_APPLIED, MFA_RESET_BY_ADMIN, mfa_enrolled, MFA_CREDENTIAL_ENROLLED and MFA_CREDENTIAL_REVOKED in the audit trail.

© AtmanID · Privacy