Single sign-on (SSO) lets the people at your facility sign in to Elevated Signals with the work account they already use, through your organization's identity provider. This guide walks you through connecting Microsoft Entra ID or Google Workspace to your facility.
What it gives you:
One account to manage. People sign in with their Microsoft or Google work account, so your identity provider's own MFA and access policies apply when they sign in.
Accounts on first sign-in. You can choose to create an account automatically the first time someone from your organization signs in, with the roles you pick.
Passwords off when you're ready. Start with single sign-on as an option, then require it once you've tested it.
Elevated Signals connects to your identity provider over OpenID Connect. Microsoft Entra ID and Google Workspace have presets that fill in most of the settings for you. The settings also offer Another OpenID Connect provider. To use it, contact support first: we have to trust your provider's address on our side, or saving fails. SAML isn't supported.
Before you start
You need three things.
The Manage single sign-on permission in Elevated Signals, and access to Facility settings. Roles that could edit facility settings when single sign-on was released have both already. If you don't see the single sign-on settings, see the first item in Troubleshooting.
Someone who can create an app in your identity provider. In Microsoft Entra ID, that's at least an Application Developer. In Google, it's someone who can create OAuth clients in a Google Cloud project that belongs to your organization.
Someone who can add a DNS record for your email domain. You'll publish one TXT record to prove you own the domain your users' email addresses are on.
If another facility already uses single sign-on for your email domain, don't start a second setup. Contact support to connect this facility to the existing one. Facilities that share a setup share its credentials, email domains and test sign-in. Each chooses its own sign-in requirement, and only one can create accounts automatically.
How setup works
In Elevated Signals, choose your identity provider and copy the redirect URI. (You have 7 days to save your setup, in the same browser, or you'll have to start again with a new redirect URI. Once you save, your redirect URI is locked in.)
In your identity provider, create an app with that redirect URI and copy its client ID and secret.
Back in Elevated Signals, paste them in and save.
Publish the DNS record we give you and verify your domain.
Run a test sign-in.
Choose whether new users get accounts automatically.
Turn single sign-on on, first as Optional, then Required.
Step 1: Open the single sign-on settings
In the menu, open Facility, then Settings.
Select Security & access. If you log in at dashboard.elevatedsignals.com, you can also go straight to Security & access. On a custom subdomain, use the same
/dashboard/settings/facility/securitypath on your own login URL.Scroll to Single sign-on and click Set up single sign-on.
Step 2: Choose your identity provider and copy the redirect URI
Under Identity provider, choose Microsoft Entra ID or Google Workspace. This guide covers those two.
Copy the Redirect URI with the copy button next to it. You'll register it in your identity provider in the next step. It stays the same when you save.
Leave this page open. Then follow the section for your provider.
Step 3a: Microsoft Entra ID
In Microsoft Entra ID
Microsoft's own guides cover each of these. Do them in the Microsoft Entra admin center:
Register an application. Follow Register an application in Microsoft Entra ID. Under Supported account types, choose Single tenant only. Elevated Signals only accepts users from your own tenant.
Add the redirect URI. Follow Add a redirect URI to your application. Choose the Web platform and paste the redirect URI you copied in step 2.
Create a client secret. Follow the client secret steps in Add and manage app credentials. Copy the secret's Value right away. Microsoft shows it only once. Note its Expires date. You'll enter it in Elevated Signals.
In Elevated Signals
Fill in the form with what you copied:
Field in Elevated Signals | What to enter | Where it comes from in Microsoft Entra ID |
|---|---|---|
Client ID | The Application (client) ID | The app registration's Overview page |
Client secret | The secret's Value, not its Secret ID | Certificates & secrets, when you create the secret |
Client secret expires on | The secret's expiry date | The Expires column next to the secret. At most 24 months away |
Email domain | The part of your users' email addresses after the @, such as | Your organization |
When you enter the email domain, Elevated Signals looks up your Microsoft Entra ID tenant and shows its Issuer URL, Tenant ID and Tenant claim (tid). You don't type these. Check the Tenant ID matches the Directory (tenant) ID on your app registration's Overview page. How to find your tenant ID shows where else to find it.
Click Save identity provider, then go to step 4.
Step 3b: Google Workspace
In Google Cloud
Google's own guides cover each of these. Do them in the Google Cloud console, in a project that belongs to your Google Workspace organization:
Limit the app to your organization. Follow Manage App Audience and set the user type to Internal, so only people in your organization can use it.
Create an OAuth client. Follow Manage OAuth Clients. Choose the Web application type. Under Authorized redirect URIs, paste the redirect URI you copied in step 2.
Copy the client ID and client secret. Google shows the full secret only when you create the client.
In Elevated Signals
Fill in the form with what you copied:
Field in Elevated Signals | What to enter | Where it comes from in Google |
|---|---|---|
Client ID | The OAuth client ID. It ends in | Google Auth Platform > Clients |
Client secret | The client secret. It starts with | Shown with the client ID when you create the client |
Client secret expires on | Keep the suggested date | Google secrets don't expire on their own. Use the date to review the secret |
Email domain | The part of your users' email addresses after the @, such as | Your organization |
Tenant ID | Your Google Workspace organization's primary domain. It's filled in from the email domain. Before you save, change it if your users sign in on a secondary domain | Your Google Workspace account |
Elevated Signals fills in the Issuer URL (https://accounts.google.com) and the Tenant claim (hd). Users from any other Google Workspace organization are refused. So are personal Google accounts.
Click Save identity provider, then go to step 4.
Step 4: Verify your email domain
Sign-ins from your domain aren't sent to your identity provider until you prove you own it.
Under Email domains, your domain shows Not verified, with the DNS record to publish: its Name, Type (
TXT) and Value.Copy the name and value with the copy buttons and publish the record at your DNS host. Your DNS host's own help explains how to add a TXT record.
Back in Elevated Signals, click Verify. Once we find the record, the domain shows Verified.
If it still says Not verified, the record may not have spread yet. Wait a few minutes and click Verify again.
If single sign-on is already Required, verifying another domain or removing a verified one moves every facility at Required on this setup back to Optional, so passwords work there again. Run a new test sign-in, then set Required again. At other facilities on the setup, their own admins set it back (see step 7).
To route more than one domain, enter it under Add an email domain, click Add domain and verify it the same way. With Google Workspace, every domain must belong to the same Workspace organization.
Step 5: Run a test sign-in
A test sign-in proves the connection works end to end. Nobody is signed in to Elevated Signals.
Under Test sign-in, click Run test sign-in. A new window opens at your identity provider.
Sign in with a work account at your verified domain.
Back in Elevated Signals, the panel shows Test sign-in succeeded. and the time under Last successful test.
If your browser blocks the window, click Open the sign-in window. If the test can't start or fails, the panel says why. See Troubleshooting at the end of this guide.
Step 6: Choose how people get accounts
Just-in-time provisioning decides what happens when someone signs in through your identity provider for the first time and has no account in Elevated Signals yet.
Off: you invite each person first. Anyone who already has an account with the same email address, at a facility that uses this identity provider, is linked to it the first time they sign in with single sign-on.
On: an account is created for them with the Default roles for new users you pick. If you pick no roles, new users can't do anything until someone gives them one.
To turn it on, tick Enable just-in-time (JIT) provisioning, choose the default roles and click Save provisioning. You can choose only active roles whose permissions you have yourself.
Just-in-time provisioning doesn't change existing accounts. It doesn't remove an account when someone leaves your identity provider either, so deactivate those in Elevated Signals. Only one facility per identity provider can provision users. If another facility already does, the panel names it instead of showing these settings.
Step 7: Turn on single sign-on
Under Require single sign-on, choose how people at this facility sign in, then click Save sign-in requirement.
Choice | What it means |
|---|---|
Off — users sign in with a password | Single sign-on is set up but not used. This is where every setup starts |
Optional — users can sign in either way | People can use single sign-on or their password |
Required — users must sign in through your identity provider | Passwords stop working for this facility's users |
Start with Optional. Let your team try it, then switch to Required.
Required becomes available once a test sign-in has succeeded. At Required, if your identity provider is unavailable, nobody at this facility can sign in. There is no emergency access yet. To restore sign-in, contact support at helpdesk.elevatedsignals.com with your facility name and the error people see.
On a GMP facility, Required is available only once electronic signatures can also be re-verified through single sign-on. Until then, the panel explains why Required isn't available.
If you later verify or remove a verified email domain, the last successful test no longer counts. Every facility at Required that shares the setup moves back to Optional. Run a new test sign-in before you require it again.
Once saved, the client ID, client secret and Tenant ID can't be edited in the settings. See You need to change the client ID, client secret or Tenant ID in Troubleshooting.
API tokens keep working when you require single sign-on. Scripts or integrations that sign in with an email address and password stop working.
How your team signs in
On the sign-in page, people enter their email address and click Continue.
Once their domain is verified and single sign-on is Optional or Required, they see Sign in with Microsoft or Sign in with Google. They click it and sign in at your identity provider.
They come back to Elevated Signals, signed in.
At Optional, the password form is still there too. At Required, people can't sign in with a password. The password form and reset link disappear only when every facility that shares your identity provider is Required. Otherwise they still show, but a password won't work.
When a session expires, the same choice appears in the sign-in dialog, and people return to the page they were on.
Troubleshooting
I can't see the single sign-on settings. If Security & access or the Single sign-on panel is missing, single sign-on may not be turned on for your facility yet. Contact support to check. If the panel says "You need the Manage single sign-on permission (sso.manage) to see or change single sign-on.", ask an administrator to add Manage single sign-on to your role.
My identity provider says the redirect URI doesn't match. Copy the Redirect URI from the panel again and paste it into your app exactly as shown.
Saving shows "This setup has expired. Register the new redirect URI shown and save again." You saved more than 7 days after the redirect URI was first shown. Register the new redirect URI the form shows in your app, then save again. If you continue setup in another browser, the form also shows a new redirect URI. Always register the one on screen.
The test sign-in failed. The panel shows Test sign-in failed: followed by an error code. Codes after sign_in_would_be_refused mean your identity provider signed the account in, but Elevated Signals would refuse it:
tenant_mismatch,tenant_claim_missingortenant_not_configured: the account isn't from the tenant this setup expects. Test with a Workspace account, not a personal one. For Google Workspace, Tenant ID must be your organization's primary domain: if it isn't, see You need to change the client ID, client secret or Tenant ID.email_unverified: your identity provider didn't confirm the account's email address.domain_not_verified: the account's email domain isn't verified yet. See step 4.
An error your identity provider names, such as invalid_client, usually means the client ID or client secret is wrong. For Microsoft Entra ID, the secret is its Value, not its Secret ID. To correct a saved one, see You need to change the client ID, client secret or Tenant ID. If the test expired or the configuration changed during it, run it again. For any other code, contact support with the code.
The domain stays Not verified. Check the record's name and value match the panel exactly, then wait and click Verify again. DNS changes can take time to spread.
Someone sees "Single sign-on isn't available for this account. Ask your administrator for access." Check each of these:
Single sign-on is set to Optional or Required, not Off.
Their email domain shows Verified.
They signed in with an account from your organization, not a personal one.
They have an active account at this facility, or just-in-time provisioning is on. If they already have an account at a facility that doesn't use this identity provider, contact support.
If they're new and just-in-time provisioning is on, none of the default roles has been archived. The panel warns "A chosen role is no longer available, so nobody new can sign in until you remove it and save." Remove that role and click Save provisioning.
Someone sees "Your organisation signs in with single sign-on, not a password. Sign in with single sign-on instead." or "Invalid email or password. If your organisation signs in with single sign-on, sign in with it instead." Their facility requires single sign-on. A password won't work, even a newly reset one. They sign in with the single sign-on button instead.
Your client secret is about to expire. Microsoft stops accepting a Microsoft Entra ID secret on its expiry date, and sign-ins through single sign-on stop with it. (Google Workspace secrets don't expire on their own.) Once saved, the single sign-on settings show the date under Client secret expires. Elevated Signals doesn't send a reminder, so put the date in your own calendar.
A saved secret can't be replaced in the settings yet. Before the date, see You need to change the client ID, client secret or Tenant ID.
You need to change the client ID, client secret or Tenant ID. Once saved, these can't be edited in the settings yet. If other facilities share your setup, contact support at helpdesk.elevatedsignals.com. Otherwise, click Remove single sign-on and set it up again from step 1, registering the redirect URI shown on screen. Removing it moves this facility to password sign-in, and accounts created by just-in-time provisioning have no password, so those people can't sign in until the new setup works. Make sure whoever does it can sign in with a password.
Nobody can sign in. If your identity provider is down or your secret has expired while single sign-on is Required, contact support at helpdesk.elevatedsignals.com with your facility name and the error people see. We can move your facility back to Optional so passwords work again. Accounts created automatically by just-in-time provisioning have no password, so those people can't sign in until single sign-on works again.