How to: Set up SSO (Single Sign-on) for your team (Admin)

This guide is for Organisation Admins for Driversnote teams that want to use Single Sign-on (SSO) for their team setup and account authorisation. If you are a team member that needs help joining your team with SSO, we have a guide aimed at your needs.

Single sign-on (SSO) lets team members sign in to Driversnote through your identity provider (IdP) using SAML. This guide shows how to configure, test, and enable SSO for your organization.

Before you begin

To set up SSO, you must:

Be an Organization Admin
Have admin access to your organization’s identity provider (IdP)
Use an IdP that supports SAML 2.0

💡Good to know: Driversnote doesn’t support domain verification yet. New members must join through a sign-up link you share.

Step 1: Find SSO settings in Driversnote

Log in to Driversnote as an admin
Open the Organization settings menu
Select Single Sign-On (SSO)

From here, you’ll be guided through the configuration flow:

Configure & Test
Activate
Share secure link

Step 2: Configure SAML

On the Single Sign-On (SSO) page, find SAML Configuration and click Configure SAML.

This opens the SSO configuration page. Follow the steps below.

Set the Default Team

Choose which team new members join the first time they sign in with SSO. You can move them to another team later.

New members will:
- Be added to the selected sub-team
- Receive the Member role by default

💡 Tip: Remember to review and adjust team assignments if your organization uses multiple teams.

Driversnote SAML details

Driversnote provides metadata that your IdP needs to establish a secure connection. You need to enter this metadata into the admin console of your IdP. You can do so in one of two ways:

Option 1: Copy links manually
- Entity ID
- Assertion Consumer Service (ACS) URL
Option 2: Upload an XML metadata file provided by Driversnote

⚠️ Note The names of these fields differ between IdP providers. For example, your IdP may call them Identifier, Reply URL, or Audience. Refer to your IdP’s documentation if you’re unsure where to place each value.

Attribute mapping

Driversnote requires specific user attributes to be sent from your IdP during login.

At this stage:

Custom attribute mapping on Driversnote side is not supported
Your IdP must send the required attributes to Driversnote using one of our supported formats

In the SSO configuration screen, you’ll find:

A list of the required attributes
Guidance on how each of them must be formatted

⚠️ Note: If your IdP does not match these requirements by default, you’ll need to adjust the attribute mapping in your IdP, not in Driversnote.

Connect your IdP metadata to Driversnote

Once your IdP is set up, return to Driversnote and connect it by:

Pasting your IdP’s metadata URL, or
Uploading your IdP’s XML metadata file

After entering the details, you can test the configuration.

Step 3: Test your SSO configuration

Before SSO can be activated, you must run a test.

Click Run test
Driversnote will save your configuration as a draft
A test login will be performed using the values you entered

Test results

✅ If the test succeeds

Your configuration is valid and is ready to be activated.

❌ If the test fails

You’ll see an error message explaining which part of the setup failed, so you know what to fix (for example, metadata, attribute mapping, or endpoints).

💡 Note: You can adjust the configuration and run the test again as many times as needed.

Saving progress while you work

If you’re not ready to finish, click Save draft. You can come back later and continue setup.

Understanding the configuration status

On the Single Sign-On (SSO) page, your SAML configuration will show a status after you start configuration:

Verified

Your configuration is verified. You can now enable single sign-on.
Draft saved

Your configuration is saved as a draft. Finish setup and run the test to verify before enabling single sign-on.

Needs attention
Something needs fixing. Edit your configuration and run the test again.

To change anything, click Edit next to the status.

Step 4: Enable SSO for your organization

Once your configuration has passed the test:

Return to the SSO overview screen by tapping ‘Save & Finish’
Toggle on Enable SSO

What happens when SSO is enabled

SSO becomes mandatory for all team members
Team members can no longer log in using passwords or other login methods
All organization admins are exempt from SSO enforcement
The secure SSO signup link becomes available for distribution within your organization

🔐 Break glass rule: Admins can always log in without SSO to prevent organization-wide lockouts. This is clearly noted next to the activation switch.

After enabling SSO, you’ll see a secure SSO signup link. Share this link with your team through your internal communication channels.

Troubleshooting and current limitations

No message log

Right now, admins can’t see a log of SSO login/sign-up attempts. Errors are shown to the team member when sign-in fails.

If a team member encounters an error, ask them to share the error message with you. You may need to adjust your IdP setup and try again.

Need help?

If you’re unsure how to configure your IdP or run into issues during setup:

Double-check your metadata and attribute mapping
Consult your IdP’s documentation

Reach out to Driversnote Support with details of your setup and any error messages you receive