Logo

Sign In to Mailzzy with Single Sign-On

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.

Read Setup GuideContact Sales

SAML 2.0 & OIDC

Okta Integration Network

Just-in-time accounts

Require SSO by domain

Okta logo
Available in the Okta Integration Network

Turn On SSO in Three Steps

Connect your identity provider once, and your whole team signs in the same way.

1

Add a connector

In Mailzzy, open Security → Enterprise SSO, click Add Connector, choose SAML 2.0 or OIDC and enter your email domains.

2

Connect your identity provider

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.

3

Activate and require SSO

Test sign-in, activate the connector, and turn on Require SSO so your domains always sign in through your identity provider.

Protocols, Controls and Providers

Everything IT needs to put Mailzzy behind your company sign-in.

Protocols

4

Standards your identity provider already uses

  • SAML 2.0
  • OpenID Connect (OIDC)
  • Sign-in from the Mailzzy login page
  • Sign-in from your identity provider's dashboard

Access Controls

4

Decide who gets in, and how

  • Require SSO for users on your domains
  • Automatic onboarding of new SSO users
  • Password-fallback (break-glass) user
  • Your identity provider's MFA and sign-in policies

Identity Providers

6

Okta, plus any SAML 2.0 or OIDC provider

  • Okta, in the Okta Integration Network
  • Microsoft Entra ID
  • Google Workspace
  • OneLogin
  • Shibboleth
  • Any other SAML 2.0 or OIDC provider
Okta Setup Guide →

One Sign-In, Any Identity 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.

Okta logo

Okta

Available in the Okta Integration Network

View on Okta →

Microsoft Entra ID

Connect through a custom SAML 2.0 or OIDC app

OneLogin

Connect through a custom SAML 2.0 or OIDC app

Ideas to Get You Started

A few common ways teams use single sign-on with Mailzzy.

Okta
→
Mailzzy

Give new marketers access on day one

When

User assigned to the Mailzzy app

Then

Account created at first sign-in

Okta
→
Mailzzy

Open Mailzzy from your Okta dashboard

When

Mailzzy tile clicked

Then

Signed in to Mailzzy

Mailzzy
→
Identity provider

Sign in from the Mailzzy login page

When

Work email entered under Sign in with SSO

Then

Signed in through your identity provider

Mailzzy
→
Identity provider

Close the password back door

When

Require SSO turned on

Then

Password sign-in blocked for your domains

Shibboleth
→
Mailzzy

Campus sign-in for university teams

When

Staff sign in with their institutional account

Then

Signed in to Mailzzy through SAML 2.0

Fallback user
→
Mailzzy

Keep a way in during an outage

When

Identity provider unavailable

Then

Password-fallback user signs in

Frequently Asked Questions about Mailzzy + SSO

Everything you need to know about setting up single sign-on for your Mailzzy team.

Which identity providers work with Mailzzy?

Mailzzy is available in the Okta Integration Network. Any identity provider that supports SAML 2.0 or OpenID Connect (OIDC) also works through a custom app, including Microsoft Entra ID, Google Workspace, OneLogin and Shibboleth.

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.

Built for Ease, Designed for Results

Mailzzy makes email marketing simple, so you can focus on what matters growing your business.

No credit card required

CTA Image

Company

Designed to meet WCAG 2.1 AAtx-ramp certification

Let's keep in touch

Sign up for our weekly email marketing newsletter and Mailzzy updates.

For more details, review our Privacy Policy

FacebookXYouTubeLinkedInInstagram

© 2026 Mailzzy. All rights reserved.

Google Play StoreApple App Store