Multi-Factor Authentication

Current status page for MFA and related identity controls in Disclosurely.

Multi-factor authentication adds a second identity check beyond a password before a user can access an application.

What Disclosurely Supports

  • MFA with an authenticator app (TOTP) is available in the current platform, alongside email-code authentication and role-based access controls.
  • SSO remains planned. Organisation-wide MFA enforcement requirements should be confirmed during procurement.
  • Buyers can use this page to separate current authentication controls from planned or customer-specific identity requirements.

What Disclosurely Does Not Claim

  • Disclosurely does not currently present enforced MFA as a generally available production control in public documentation.
  • Availability of SMS codes, hardware security keys and recovery workflows should be confirmed separately; TOTP availability does not imply support for those methods.
  • Disclosurely does not claim that MFA alone resolves access governance, user provisioning, or investigation-role design.

Procurement Checklist

  • Ask whether enforced MFA is available for the deployment you are buying.
  • SSO and identity-provider integration are planned, not currently available.
  • Review password, invitation, and session behaviour.
  • Confirm how administrator and case-handler roles are assigned and revoked.
  • Document any organisation-wide enforcement or recovery requirements.

FAQs

Is MFA available today?

Yes. TOTP MFA is available in the current platform. Confirm organisation-wide enforcement requirements separately.

Should buyers require MFA?

Many enterprise buyers expect MFA for administrative access. If MFA is required by policy, record that requirement during security review.

What controls matter if MFA is not yet available?

Review password handling, session controls, least-privilege permissions, administrator access, user offboarding, and audit history.

Related Trust Centre pages

Commercial review paths