Single Sign-On (SSO) is now available

We’re pleased to announce that Single Sign-On (SSO) is now available on our platform.

This feature was added directly in response to customer feedback. Many of our customers told us that SSO was important for improving security, simplifying access management, and aligning our platform with their internal IT standards. We listened, prioritised this work, and are happy to make SSO available as a supported option.

We remain very open to feedback and feature requests from our customers. If there are capabilities you would like to see added or improved, please let us know through our usual support channels.

What if you don’t use SSO?

If your organisation does not use SSO, or is not yet ready to enable it, no action is required.

You can continue to log in as normal. The only change you may notice is that your password is now asked for after providing your email, this is part of an updated and more secure authentication flow. No changes are required to your account or user setup.

High-level SSO setup requirements

We support SSO via OpenID Connect (OIDC). To configure SSO for your organisation, we will need the following information.

Identity provider configuration

You will need to register our platform as an application in your OpenID Connect identity provider. This could be Entra ID (Azure AD), Google, or any other OIDC-compliant provider your organisation uses.

From this registration, we will need to securely receive:

• Client ID 
• Client Secret

OIDC endpoints

We will also require details of your OIDC configuration, such as:

• Issuer URI 
• Endpoint details, or 
• A .well-known/openid-configuration (OpenID Connect discovery) endpoint

Claims requirements

Your identity provider configuration must meet the following claim requirements:

• An email claim named email must be provided 
• A groups claim can optionally be provided as a list ([])

If you would like us to restrict access to only a specific group of users, please let us know:

• Which group should be allowed access, and 
• The exact value of that group as sent in the groups claim

Email domains

We will need a list of approved email domains used by your organisation (for example, @yourcompany.com).

Scopes

By default, we request the following OIDC scopes:

• openid 
• profile 
• email

How to get started

If you are interested in enabling SSO for your organisation, please raise a support ticket.

Once we receive your request, our team will reach out to you to collect the required information securely and guide you through the setup process.