Let your team sign in with the work account they already use. Connect Okta or any SAML 2.0 or OIDC identity provider, and manage who can access Mailzzy from one place.
SAML 2.0 & OIDC
Okta Integration Network
Just-in-time accounts
Require SSO by domain
Connect your identity provider once, and your whole team signs in the same way.
In Mailzzy, open Security → Enterprise SSO, click Add Connector, choose SAML 2.0 or OIDC and enter your email domains.
Add Mailzzy from the Okta catalog, or create a SAML 2.0 or OIDC app in your identity provider. Then assign the people who need access.
Test sign-in, activate the connector, and turn on Require SSO so your domains always sign in through your identity provider.
Everything IT needs to put Mailzzy behind your company sign-in.
Standards your identity provider already uses
Decide who gets in, and how
Okta, plus any SAML 2.0 or OIDC provider
Add Mailzzy from Okta, Microsoft Entra ID and other app catalogs. Connect any other SAML 2.0 or OIDC provider through a custom app.
Connect through a custom SAML 2.0 or OIDC app
Connect through a custom SAML 2.0 or OIDC app
A few common ways teams use single sign-on with Mailzzy.
User assigned to the Mailzzy app
Account created at first sign-in
Mailzzy tile clicked
Signed in to Mailzzy
Work email entered under Sign in with SSO
Signed in through your identity provider
Require SSO turned on
Password sign-in blocked for your domains
Staff sign in with their institutional account
Signed in to Mailzzy through SAML 2.0
Identity provider unavailable
Password-fallback user signs in
Everything you need to know about setting up single sign-on for your Mailzzy team.
Yes. You can set up a SAML 2.0 or an OIDC connector. Both support sign-in from Mailzzy, sign-in from your identity provider's dashboard and automatic account creation. Only one connector can be live at a time.
SSO is available on Mailzzy plans that include Enterprise SSO. A Mailzzy administrator sets it up in Security → Enterprise SSO. If the tab says SSO isn't included in your plan, contact us.
Yes. Turn on Require SSO for users on these domains to block password sign-in for your email domains. One password-fallback user keeps password access in case your identity provider is unavailable.
Mailzzy can create an account the first time an assigned user signs in (just-in-time provisioning). SCIM provisioning isn't supported yet, so deactivate departing users in Mailzzy as well as in your identity provider.
Your password-fallback user can still sign in with a password and pause the connector in Security → Enterprise SSO, or you can email support@mailzzy.com to turn SSO off for your account. Protect the fallback account with two-factor authentication.
No. SSO is only for team members who sign in to Mailzzy. Your contacts and subscribers keep receiving emails and managing their preferences as usual.
Let's keep in touch
Sign up for our weekly email marketing newsletter and Mailzzy updates.
For more details, review our Privacy Policy