Implementing 2FA with Manifestly authentication
Two-factor authentication adds a second check on top of a password. Manifestly's own accounts do not have built-in 2FA, so the way to get it is to put an identity provider in front of Manifestly and let that enforce it.
The recommended route
Set up SSO and require 2FA at the identity provider. Everyone signing in to Manifestly then passes through your provider's second factor, and you manage the policy in one place for every system your team uses rather than per application.
This is better than per-application 2FA for reasons that matter when somebody leaves: disabling their account at the provider cuts access to everything at once, and there is no separate Manifestly credential still working.
How to get there
- Google Workspace: turn on 2-step verification in Google, then set up Google SSO. See Implementing SSO with Google.
- Okta: see Setting up SAML based SSO with Okta.
- Azure AD / Entra ID: see Setting up SAML based SSO with Azure AD.
- Another provider: see Setting up SAML based SSO – Using Your Own IdP.
SSO is an Enterprise feature.
If SSO is not an option
Without SSO, the password is the only barrier, so the basics carry more weight: unique passwords in a password manager, and prompt removal of people who leave. See Managing Users and Their Permissions.
Note that some actions inside Manifestly ask you to confirm a one-time code sent to you, as a check on sensitive changes. That is a per-action confirmation rather than sign-in 2FA, and it is not a substitute for it.