Multi-factor authentication availability
2 min read
Updated Apr 12, 2026
The current security settings page is explicit: authenticator-based multi-factor authentication is planned, but not yet configured for workspace access in the current rollout. This article exists to prevent mistaken rollout assumptions.
Before you begin
A need to answer an MFA question accurately
Awareness of the difference between planned and live features
A fallback account-security plan for the present rollout
Read the current product state literally
Security settings label MFA as coming soon rather than presenting it as a live self-serve control.
That means teams should not plan rollout milestones around in-product MFA enrollment yet.
Use current controls instead
Today, account access is centered on email and password plus workspace membership checks.
Other security controls such as link restrictions, session visibility, and compliance settings remain relevant even without live MFA.
Escalate enterprise needs early
If your organization needs stronger identity controls immediately, discuss enterprise identity planning instead of waiting silently for MFA.
That conversation may include SSO coordination or rollout timing questions.
Pro Tips
Do not publish internal documentation that assumes MFA enrollment already exists in the app.
Pair MFA discussions with SSO planning if your organization is larger or more regulated.
Keep current password reset and owner access paths documented while MFA is still planned.
Was this article helpful?
Use this as a quick signal while the public knowledge base is static.