Single Sign-On Setup Guide
An outline of the steps to configure your identity provider to work with the Join platform for single sign-on (SSO)
1. Configuring SSO for Join
To set up SSO for your company, complete the form linked below. It includes instructions for any pre-setup required for your identity provider. Once submitted, our Support Team will reach out to coordinate either additional configuration actions or the steps outlined below.
Join currently supports the following identity providers and protocols. Single Sign-On (SSO) is a centralized authentication method that lets users access Join using credentials from their existing identity provider, without needing a separate Join password:
- Identity Providers: Microsoft Entra ID, Okta, Google Workspace
- Protocols: SAML 2.0
Note: Don’t see your identity provider listed? Please contact our Support Team, as we continually evaluate which providers to support.
2. Communicating the Change to Your Users
We recommend notifying your Join users of the switch to single sign-on, as their login experience will look slightly different. They’ll typically no longer need to enter a password to access Join, since they’ll already be authenticated with your identity provider. You can find a full list of your Join users in the Company Administration portal; your Join company admin can assist with access.
Sample Email
<Company Name>,
At <insert time> on <insert date>, we will be turning on Single Sign-On (SSO) for Join.
After this date, when logging into Join after entering your email on the login screen, you may be redirected to authenticate with your <insert identity provider> credentials rather than your current Join password.
On most occasions, since you are already authenticated through SSO, you will only need to enter your email address on the login page to access Join.
If you have trouble logging in, contact the Join Support team at support@join.build.
Tip: Be on the lookout for users who may have changed their emails. They are likely still using their old email address with Join, and when they log in via SSO, they will no longer have access to their projects. We can work with you to resolve this before enabling SSO.
3. Enabling and Testing the SSO Connection
When it is time to go live, our Technical Support team will flip the switch to enable SSO for your company. We’ll email you to let you know SSO is live and ask you to test logging into Join to ensure everything works as expected.
Anyone in your organization can test, regardless of whether they have an existing Join account. If you don’t have an existing account, we’ll automatically create one during the authentication process.
Caution: Microsoft Entra ID customers: If you have Admin consent requests enabled, a Microsoft Entra ID admin will need to approve the app once the first user has logged in.