Skip to main content
Single sign-on (SSO) lets members sign in to your community with the credentials your organisation already manages. They don’t need a separate Zapnito password, and you keep control of access in your own identity provider. Zapnito works with the identity providers organisations already use and with the open standards they are built on. If your provider isn’t listed here, get in touch and we’ll check it with you.

​
Supported identity providers

Zapnito supports common identity providers, including:
  • Okta
  • Microsoft Entra ID
  • Auth0
  • Salesforce
Any other provider that supports one of the protocols below can also connect to your community.

​
Supported protocols

Zapnito supports three standard protocols. Most providers support more than one, so the choice usually comes down to your organisation’s policy. Not sure which to use? Tell us which provider you have and we’ll recommend one.

​
What you can do with SSO

  • Create accounts automatically. When a member signs in with SSO for the first time, Zapnito creates their account. You don’t need to invite them first.
  • Map details to your community. Map information from your identity provider, such as profile details and groups, to the matching fields and groups in your community. Groups control permissions, so this can decide what each member can access.
  • Require SSO. Turn off email and password sign-in so every member signs in through your identity provider.
  • Support single logout (SLO). When a member signs out of your community, Zapnito can also end their session on your identity provider. To support this, give us an endpoint URL that accepts a GET request and destroys the current browser session on your identity provider.
Test SSO with a small group before you require it for everyone. Once SSO is required, members can only sign in through your identity provider.

​
What changes when SSO is on

Once SSO is enabled, some parts of the member journey move from Zapnito to your identity provider.

​
Set up SSO

We configure SSO for your community with you. Your identity team doesn’t need to build anything.
1

Choose a provider and protocol

Decide with your identity or IT team which provider your members will sign in with, and which protocol to use. We can help you choose.
2

Tell us what you need

Contact your Zapnito account manager or support. Tell us:
  • Your identity provider and preferred protocol.
  • Which members should have access.
  • Which details to map to your community, such as profile fields or groups.
  • Whether to create accounts automatically, and whether to require SSO.
  • Whether you need single logout (SLO). If you do, include the endpoint URL that ends the session on your provider.
3

Register Zapnito with your provider

We confirm the details we need from your provider for your protocol, and send you the details your provider needs to recognise your community.
Don’t send secrets, such as client secrets, by email. We’ll agree a secure way to share them.
4

Test and roll out

Sign in with a small group of members, check that their accounts and groups are correct, then roll SSO out to everyone.

​
Next steps

  • Authentication: SSO controls how members sign in. API requests still use an API token.
  • Zapier integration: connect your community to the other tools your organisation uses.