Skip to main content
MultiMFA logoMultiMFA
All Guides

MultiMFA Authenticator

Set up MultiMFA Authenticator with individual browser-based TOTP vaults, seat management, clean-room policies, invites, and audit-ready logs.

Best for: Teams that need individual authenticator app access without personal phones.

Overview

MultiMFA Authenticator is a web-based authenticator app inside MultiMFA. Each licensed user gets a private TOTP roster managed by the organization.

Finding this in the dashboard

After you log in, click MultiMFA Authenticator in the dashboard sidebar. Seat purchase, invites, policies, and each user’s vault all live on that page.

Step-by-step setup

  1. Step 1

    Open MultiMFA Authenticator and purchase seats

    Click MultiMFA Authenticator in the dashboard sidebar. An owner, admin, or authorized manager then chooses monthly or yearly per-seat billing.

  2. Step 2

    Invite users by email

    Reserve seats and send invitations to the employees who need phone-free TOTP access.

  3. Step 3

    Accept the invitation

    Each user signs in or creates an account, accepts the invite, and receives access to their private Authenticator dashboard.

  4. Step 4

    Add authenticators

    Users add standard TOTP entries by QR image upload, camera scan, clipboard image paste, otpauth URI paste, or manual setup key entry, depending on browser support and organization policy.

  5. Step 5

    View rolling codes in the browser

    Users view their own live TOTP codes in MultiMFA without using personal phones or consumer browser extensions.

  6. Step 6

    Manage seats, policies, and audits

    Managers maintain active seats, revoke unused access, tune clean-room policies, and review audit records.

Best practices

  • •Use one licensed seat per active user; do not share user accounts.
  • •Keep each user’s TOTP enrollments individual unless the account is truly shared.
  • •Use MultiMFA TOTP, not Authenticator, when one shared account needs one shared authenticator code.
  • •Use MultiMFA SMS when the target system only supports SMS MFA.
  • •Review seat and audit activity after staffing or contractor changes.
  • •Confirm the target application supports standard TOTP enrollment before planning rollout.

Common troubleshooting

  • •If QR capture fails, try brighter display settings, clipboard paste, otpauth URI paste, or manual setup key entry.
  • •If a code is rejected, wait for the next time window and verify the target service uses standard TOTP.
  • •If a user cannot access Authenticator, confirm their invite was accepted and their seat is active.
  • •If a service only supports SMS, push-only, passkeys, or proprietary app approvals, choose the matching MFA workflow instead.