How to set up single sign-on (SSO)
A team administrator opens SSO in the left menu, chooses SAML 2.0 or OpenID Connect, copies the values shown into the identity provider, verifies the company e-mail domain with a DNS TXT record and clicks Turn single sign-on on. Members then use Sign in with SSO on the login page.
Plan: Unlimited and the Deal Room Pass – not the trial, Pro or Max. See plans
Steps
- As a team administrator, open SSO under Settings in the left menu.
- Under Protocol choose SAML 2.0 or OpenID Connect.
- SAML: copy the Entity ID (Audience) and ACS URL (Reply URL) into a new SAML application in your identity provider (Name ID = the user’s e-mail), then paste the IdP metadata URL, upload the metadata XML or enter the values by hand. OpenID Connect: add the Redirect URI in a new web application, then enter the Issuer URL, Client ID and Client secret. Click Save.
- Under Verified e-mail domains click Add domain, add the TXT record shown to your DNS and click Verify.
- Click Turn single sign-on on. It needs finished identity-provider settings and at least one verified domain.
- Optional: tick Require SSO for members with these domains to refuse password and Google sign-in for them, and generate a token under User provisioning (SCIM 2.0) for Okta or Microsoft Entra ID.
Opens the right page in HelpRange. New to HelpRange? Sign up first – 7-day free trial, no card.
Open SSO settingsHow members sign in
On the login page members click Sign in with SSO and enter their work e-mail, or use the team’s Direct login address for your team: shown on the SSO page. New people from verified domains join the team on their first SSO sign-in (just-in-time); addresses that already belong to another HelpRange team are never moved.
Require SSO
With Require SSO for members with these domains on, password and Google sign-in are refused for those addresses and their open password / Google sessions end. The team owner keeps password sign-in as a break-glass account.
Limits and good to know
- Up to 20 verified e-mail domains per team; a domain can be verified by one team only.
- Signatures must be SHA-256 or stronger – SHA-1 is rejected.
- SCIM groups are stored but do not change roles or folder access; the last administrator cannot be deactivated through SCIM.