Skip to content
Open Bluedeer

Set up single sign-on (SSO) for your workspace

How the workspace owner connects the company's identity provider with SAML or OpenID Connect, chooses which domains sign in with it, runs a test sign-in, makes a domain SSO-only, replaces the provider safely, and removes it again.

Single sign-on lets people with an address on your company's domains sign in to Bluedeer through your identity provider, such as your company's own sign-in system. Only the workspace owner can change it. Admins can see every setting, read-only: each control they can't use says "Only the workspace owner can change single sign-on." when they point at it or move to it with the keyboard, and on the phone the screen says so at the top. Members don't see it, and the personal workspace doesn't have it.

  • On the web: open the Workspace page, select Settings, and choose the Security tab. Single sign-on is below Require two-step sign-in.
  • On the phone: open Manage workspace, and on General tap Single sign-on under Rules.

Both show the same settings.

Before you start

Your company's domain must be a verified domain of this workspace. Only its DNS TXT record verifies a domain; an email address on it never does. Add the domain under Verified domains first: Verify a domain for your workspace.

Only one Bluedeer workspace can use a domain for single sign-on, and public email domains can't use it.

1. Add Bluedeer to your identity provider

Under Details for your identity provider, Bluedeer shows the values your IT admin enters when they add Bluedeer as an app. Each has a Copy button. All of them are on Bluedeer's own address.

  • SAML 2.0: the ACS URL (reply URL), the Entity ID (audience) and the Metadata URL. Send the person's email address as the NameID or as an email attribute.
  • OpenID Connect: the Redirect URI.

2. Enter your identity provider's details

Under Identity provider, choose the protocol:

  • SAML 2.0: enter the identity provider's Metadata URL, or paste its metadata XML.
  • OpenID Connect: enter the Issuer URL, the Client ID and the Client secret.

Select Save. Bluedeer says "Saved. Run a test sign-in to make sure it works." The switch next to Identity provider turns single sign-on on or off. When it is off, nobody can sign in with it.

To change the provider later, enter the new details and save again. For OpenID Connect, leave Client secret empty to keep the saved one, and use Refresh issuer to read the issuer's settings again. A changed provider needs a new test sign-in. If a domain is SSO-only, the new provider doesn't replace the current one straight away: see Change the provider while SSO-only is on.

While SSO-only is on, a new provider is not used straight away. Bluedeer says "Saved as pending. Run a test sign-in with the new provider below." and shows New provider, waiting for a test sign-in. People keep signing in with the current provider until a test sign-in with the new one works. Select Test sign-in with the new provider: when it works, the new provider replaces the current one. Select Discard to drop the pending provider and keep the current one.

3. Choose which domains use it

Under Domains, each of the workspace's domains shows whether its DNS record is there:

  • Verified: switch it on to send sign-ins with an address on that domain to your identity provider. Other ways of signing in still work.
  • Not verified yet: add the TXT record shown to the domain itself (not a subdomain), then select Check now. DNS changes can take a few minutes.
  • DNS record missing: the record was there but is gone. Single sign-on for that domain ends on the date shown unless you add the record back. The workspace's members are told in their Inbox.

4. Run a test sign-in

Under Test sign-in, enter a work email address on one of the domains you switched on and select Test sign-in. Your identity provider opens as it does for a real sign-in. When you come back, Bluedeer says whether it worked, for example "It works: your identity provider signed in [email protected]." A test signs nobody in and adds nobody to the workspace.

The test needs single sign-on switched on and at least one domain using it.

Make a domain SSO-only

When a domain uses single sign-on, an SSO-only switch appears under it. SSO-only means everyone with an address on that domain can sign in only with your identity provider. Before it turns on, Bluedeer shows what will happen:

  • Password, Google, Apple, passkeys, emailed codes and password reset are switched off for those people. They are not deleted, and turning SSO-only off brings them back.
  • Everyone on the domain is signed out on every device straight away, including you if your address is on it.
  • How many people in the workspace are on the domain, how many haven't used single sign-on yet, and how many people outside the workspace on that domain are affected.

To turn it on, a test sign-in must have worked, and you must type the domain to confirm. People who haven't used single sign-on before get a code by email the first time, to connect it to their account.

Change the provider while SSO-only is on

When a domain is SSO-only, a provider that doesn't work would lock everyone on that domain out. So while SSO-only is on, Bluedeer saves a new provider as pending instead of replacing the current one. Before you save, the form says so.

  1. Enter the new provider's details and select Save. A New provider, waiting for a test sign-in card appears. The current provider keeps signing everyone in.
  2. On that card, select Test sign-in with the new provider and sign in with a work address on one of the workspace's SSO domains.
  3. If the test works, Bluedeer says "The test sign-in worked. The new provider now signs everyone in." The new provider replaces the old one straight away, already tested, and SSO-only stays on.

If the test fails, nothing changes: the current provider keeps working, and you can fix the details, save again and test again. Saving again replaces the pending provider. If you change or discard the pending provider while a test is running, that test replaces nothing. To give up on it, select Discard on the card. Removing the identity provider removes a pending one too.

When no domain is SSO-only, saving replaces the provider straight away, as described above, and you run a test sign-in afterwards.

If single sign-on stops working while SSO-only is on

If the identity provider breaks while a domain is SSO-only, nobody on that domain can sign in, the owner included when their address is on it. Email [email protected] from the owner's address, and Bluedeer support will help you get back in after checking that the request comes from the owner. Once you can sign in again, fix the provider, run a test sign-in and switch SSO-only back on. To avoid this, change the provider only through a pending provider and its test sign-in (above), and keep the SSO-only domain's DNS record in place.

How people sign in

On the sign-in page, people enter their email address and select Continue. If their domain uses single sign-on, Bluedeer offers Continue with SSO, with Use a password instead below it. If the domain is SSO-only, Bluedeer goes straight to the identity provider.

Remove the identity provider

Select Remove under Identity provider and confirm. Nobody can sign in with single sign-on until you add a provider again, and SSO-only ends on every domain, so people there sign in with their other methods again.

Single sign-on and two-step sign-in

Signing in to Bluedeer with the workspace's single sign-on never asks for Bluedeer's own 6-digit code, even if the person has turned on two-step sign-in for their account: your identity provider handles the second step.

If the workspace requires two-step sign-in (an Enterprise setting), a sign-in with the workspace's single sign-on meets that rule, for as long as that sign-in lasts. It counts per sign-in, not for the account: if the same person signs in with a password, Google or Apple instead, they need two-step sign-in or a passkey on their Bluedeer account to open the workspace.

Add and remove people automatically

With single sign-on set up, the owner can also turn on directory sync on the web, which is part of Bluedeer Enterprise. It lets your identity provider automatically add people to the workspace and remove them: Add and remove people automatically with directory sync (SCIM).