Setting up Single Sign-On (SSO) will require you to access some technical information from the admin settings of your Identity Provider, you will likely need the assistance of the team that manages that system to get that information. 

Alongside Azure AD, we support the following Identity Providers:

1. How to find the identity provider information

There are two ways to provide this information, you can provide us with your IdP metadata file, or follow the steps below:

1. Navigate to your applications manager in Azure AD, then select 'New application':

2. To add as an app, you will then need to select 'Non-gallery application', this will prompt you to name the new application, for this example, we named it '', you can then click 'Add'

3. After creating your App, the first step is to add users and groups to it, simply click the first step in the Getting Started menu of your App Overview page:

4. Next, click to set up Single Sign-On, on the next page select the box that says SAML:

5. After that, you'll then need to configure access to the live environment, by applying the following settings in Azure AD: 

  • The Assertion Consumer Service (ACS) URL (this is the URL where will receive the response from the identity provider): 


  • The Entity ID of the live instance of 


For Customers in the APAC Region please use the following settings:

  • The Assertion Consumer Service (ACS) URL (this is the URL where will receive the response from the identity provider):


  • The Entity ID of the live instance of 


This is where you need to apply the new settings, by clicking 'edit'

You can fill in the <ORGANISATION>part with your desired subdomain (e.g. Facebook would likely want their subdomain to be

7. Next step would be to provide us with the following information: (Note: we need the entire URLs, not just the parts that are not blurred.)

In Azure AD:

SSO Target Url =  Login URL

Entity IDAzure AD identifier

7.a If your certificate has expired you must create a 'New Certificate' and then activate it by clicking the three dots and then selecting 'Make Certificate Active'

Note: Once you have the above information, please email it to so we can configure SSO on our end.

2. Mapping Attributes

For your SSO login to work, attributes in Azure AD need to be mapped correctly, inside the SSO settings for your app (apps> > Single Sign-On > SAML)

1. Scroll down to Step 2, click  'edit'

2. Your attributes should be mapped in the following way:

3. Next, you need to set the name identifier format to 'persistent'. In the same page, click into the 'Unique User Identifier (Name ID)':

  •     Also, set Source Attribute to 'user.objectid'

3. Accessing via SSO

Organisations using SSO will access via a sub-domain. This is a change to how you access at the moment. 

Rather than going to, once SSO is activated you will be able to access the system at:  


This ensures that we can always redirect your users to the correct identity provider when they sign in or access the system for the first time. 

4. New User Templates

SSO with comes with an exciting new feature, New User Templates!

This feature will allow you to provision a non-existing SSO user with work areas and access upon their initial login. This is great for admins that want to automate the process of assigning users work when they are created.

See here to find out how to utilise New User Templates.

To note:

  • Either the assertion, response or the assertion and response must be signed 
  • SHA-1 & SHA-256 algorithms are supported for the signature and digest. We recommend the use of SHA-256 as best practice 
  • SSO can be initiated from the service provider or the identity provider 
  • Encrypted assertions are not supported 

If you have any further questions following the completion of your setup, please don’t hesitate to contact the support team at