Single sign-on
With single sign-on your people sign in to RefinePoint with the account they already use at work. You decide who may join, and you can require it for everyone from your company. It is part of the Enterprise plan and is managed in Settings, Single sign-on by owners and admins.
RefinePoint supports SAML 2.0 and OpenID Connect, so it works with Okta, Microsoft Entra ID (Azure AD), Google Workspace, OneLogin, Ping and most others.
Set it up
Section titled “Set it up”
- In Settings, Single sign-on, choose SAML 2.0 or OpenID Connect.
- Add RefinePoint to your identity provider (see the steps for your provider below).
- Paste what your provider gives you back into RefinePoint and choose Connect.
- Under Email domains, add your company’s domain, for example acme.com.
- Add the TXT record shown to your domain’s DNS, wait a little, and choose Verify.
- Choose Test sign-in. You are taken to your provider and back. A green result means it works.
- Optionally switch on Require single sign-on, choose whether new people can join on their own, and map groups.
Email domains
Section titled “Email domains”A domain is yours once you prove it. RefinePoint shows a TXT record with a name (like
_refinepoint-verification.acme.com) and a value. Add it where your domain’s DNS is managed, then choose
Verify. DNS changes can take up to an hour. Only one workspace can verify a domain, and public mail services such as
Gmail cannot be verified.
Once a domain is verified, anyone entering an address in it on the Sign in with SSO page is sent to your provider.
Who can join, and who must use it
Section titled “Who can join, and who must use it”| Choice | What it does |
|---|---|
| Require single sign-on | People with an address in a verified domain can open the workspace only by signing in through your provider. A password sign-in is refused with a message that tells them what to do. You need a verified domain and a successful test first, so you cannot lock yourself out. |
| New people from your domains: need an invitation | Only people you invite become members. |
| New people from your domains: join when they first sign in | Anyone who signs in through your provider with an address in a verified domain joins at once, with the role you choose (Member, Viewer or one of your own roles). Seats on your plan still apply. |
Guests with other email addresses keep signing in the usual way and are invited as before.
Group mapping
Section titled “Group mapping”If your provider sends groups, map each group name to a group in RefinePoint. On every sign-in people are added to the mapped groups they belong to, and removed again when the provider stops sending the group. Groups you gave someone by hand are never removed.
Setting up your provider
Section titled “Setting up your provider”- In Okta, choose Applications, Create App Integration, then SAML 2.0.
- Set Single sign-on URL to the RefinePoint ACS URL and Audience URI to the Entity ID.
- Set Name ID format to EmailAddress and Application username to Email.
- Add attribute statements email, firstName and lastName. For groups, add a group attribute named groups.
- Finish, assign the people or groups who may sign in, and copy the Metadata URL from the Sign On tab into RefinePoint.
Microsoft Entra ID
Section titled “Microsoft Entra ID”- In the Entra admin center, choose Enterprise applications, New application, Create your own application.
- Open Single sign-on, choose SAML, and edit Basic SAML Configuration: Identifier is the RefinePoint Entity ID, Reply URL is the ACS URL.
- Check that the Unique User Identifier is the user’s email (user.mail).
- To send groups, add a group claim in Attributes and Claims and name it groups.
- Copy the App Federation Metadata URL into RefinePoint, and assign the people who may sign in under Users and groups.
Google Workspace
Section titled “Google Workspace”- In the Google Admin console, choose Apps, Web and mobile apps, Add app, Add custom SAML app.
- On the Google identity provider page, download the metadata file. In RefinePoint, upload it.
- For the service provider details, enter the ACS URL and Entity ID from RefinePoint, and set Name ID format to EMAIL.
- Map the attributes: Primary email to email, First name to firstName, Last name to lastName.
- Turn the app ON for everyone (or the groups who may sign in).
Another provider
Section titled “Another provider”Use SAML 2.0 with the details RefinePoint shows, or OpenID Connect: create a web app in your provider, give it the Redirect URI shown, and enter the issuer URL, client ID and client secret. If your provider names its attributes differently, change them under Attribute names.
Signing in
Section titled “Signing in”People choose Sign in with SSO on the RefinePoint website, enter their work email, and are taken straight to their company’s sign-in. If they already had a RefinePoint account with the same email, it is linked to their work account.
If something goes wrong
Section titled “If something goes wrong”| What you see | What to do |
|---|---|
| “We could not find the TXT record yet” | Check the name and value exactly, and wait up to an hour. |
| Test sign-in says the domain is not verified | Verify the domain of the address you signed in with. |
| “This workspace requires single sign-on” | Sign out, choose Sign in with SSO and enter your work email. |
| A new person cannot join | Check that joining on first sign-in is chosen and that the workspace has a free seat. |
Every change to these settings is written to the audit log.