Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

SAML single sign-on

Set up SAML single sign-on so your team signs in to Zerve through your identity provider.

With single sign-on (SSO), people in your organization sign in to Zerve through your company's identity provider, such as Microsoft Entra ID (Azure AD), Okta or Google Workspace, instead of a separate Zerve password. Anyone signing in with an email address on your domain is sent to your identity provider.

Set up SSO in Settings → SSO. You need to be an organization admin, and you'll need someone who can configure your identity provider.

SSO may not be available on every plan. If you don't see SSO in Settings, contact Zerve.

Before you start

You'll need:

  • The email domain your team signs in with, such as acme.com

  • Admin access to your identity provider, or someone who has it

  • Your identity provider's SAML metadata URL, which you'll get during setup

Set up SSO

1

Create the connection in Zerve

In Settings → SSO, create a new connection. Enter:

  • A name for the connection

  • The email domain to send through SSO

  • The provider type: SAML, or Azure AD if you use Microsoft Entra ID

2

Copy Zerve's details

Zerve shows two values. Copy them:

  • Entity ID

  • ACS URL (the Assertion Consumer Service URL)

3

Configure your identity provider

In your identity provider, create a new SAML application for Zerve, and enter the Entity ID and ACS URL from Zerve.

Assign the application to the people or groups who should have access.

4

Give Zerve your identity provider's metadata

Copy your identity provider's metadata URL for the new application, and paste it into Zerve.

If your identity provider sends people's email address and name in non-standard claims, tell Zerve which claims to use for email and name.

5

Finish

Zerve fetches and checks your identity provider's metadata straight away. If it can reach the URL and the metadata is valid, SSO is set up. If not, you'll see an error; check the URL is correct and reachable from the internet, then try again.

After setup

People signing in with an email address on your domain are sent to your identity provider. An organization can have one SSO connection.

Multi-factor authentication

People who don't sign in through SSO can turn on multi-factor authentication for their own account. With SSO, multi-factor authentication is handled by your identity provider.

Self-hosted Zerve

If your organization runs its own Zerve install, it can use your own OIDC identity provider instead. See Self-managed installs.

Last updated

Was this helpful?