Skip to main content

Single Sign On in Upbound

Enterprise Plan Feature

This feature is available in the Enterprise Plan and above. For more information, see our pricing plans or contact our sales team.

Single sign-on (SSO) lets members of your Upbound organization sign in through your company's identity provider (IdP), such as Okta, Microsoft Entra ID or Google Workspace. Directory sync goes one step further: it adds and removes members and teams in Upbound as your directory changes.

Organizations use SSO to:

  • Keep sign-in, multi-factor authentication and password policy in one place.
  • Give people access to Upbound by assigning them in the IdP, without invitations.
  • Make sure only people your IdP approves can reach the organization.

Organization owners set up SSO themselves in the Upbound console.

Who can use SSO​

EnterpriseBusiness Critical
Single sign-onYesYes
Directory syncNoYes

Only organization owners can set up, test and turn on SSO. Other members can open the SSO page in the console but can't change anything on it.

See Upbound pricing to compare plans.

How SSO works in Upbound​

SSO in Upbound rests on two things your organization sets up and one switch an owner turns on.

Verified domains. A verified domain is an email domain, such as example.com, that your organization has proven it owns. Upbound only sends people to your IdP when their email is on one of your verified domains, and only accepts sign-ins from your IdP for those domains.

The identity provider connection. The connection links your IdP to Upbound over SAML or OpenID Connect (OIDC). Your IdP decides who can sign in: anyone you assign to the Upbound app in your IdP can sign in to your organization.

Turning SSO on. You can verify domains and connect your IdP without affecting anyone. Nothing changes for members until an owner turns SSO on. When SSO is on:

  • Upbound signs everyone out once when SSO is turned on, including the owner who turned it on.
  • Members sign in through your IdP. SSO sign-in is exclusive, so other ways to sign in to Upbound, such as a password or social sign-in with GitHub or Google, stop working for them.
  • Invitations turn off. Your IdP manages membership. Upbound deletes pending invitations when SSO turns on.
  • People join by signing in. The first time someone assigned to the Upbound app in your IdP signs in, Upbound creates their account if needed and adds them to the organization as a member.
  • Directory sync keeps members and teams in step. On Business Critical, directory sync syncs members and teams directly from your directory, so people have access before they first sign in.
  • Upbound support keeps access through Upbound's own SSO, so support can still help you.

Set up SSO​

In the Upbound console, select SSO Provider in your organization's sidebar. The page walks you through four steps in order. Each step unlocks when the step before it finishes.

Some steps happen in a setup portal that Upbound opens for you. WorkOS, Upbound's SSO partner, provides the portal. When you finish in the portal, it returns you to the SSO page in Upbound.

Before you begin​

You need:

  • The owner role in an Enterprise or Business Critical organization.
  • Access to your company's DNS settings, or someone who can add a DNS record for you.
  • Administrator access to your IdP, to create the Upbound app and assign people to it.
  • An account in your IdP with the same email as your Upbound account, on the domain you plan to verify.

Step 1: Verify your domain​

Verify that you own the email domains your members use to sign in.

  1. In Verify your domain, open the setup portal.
  2. Follow the portal's instructions to add a DNS record for your domain.
  3. Return to Upbound. The domain shows as pending until the DNS check passes, then as verified.

Repeat this step for every email domain your members use. For details on verifying a domain in the setup portal, see the WorkOS domain verification guide.

Step 2: Connect your identity provider​

  1. In Connect your identity provider, open the setup portal.
  2. Choose your IdP and follow the portal's guide for it. Any SAML or OIDC provider works.
  3. In your IdP, assign the people who need Upbound access to the Upbound app.
  4. Return to Upbound. The step finishes when the connection is active.

For setup steps and screenshots for your IdP, find it in the WorkOS integrations guides. If your IdP isn't listed, use the generic SAML or OIDC guide.

Step 3: Test sign-in​

Sign in through your IdP once, as yourself, to confirm it works for your account before everyone depends on it.

  1. In Test sign-in, start the test.
  2. Sign in to your IdP with the account that has your Upbound email.
  3. Upbound returns you to the SSO page with the result.

The test doesn't sign you in, sign you out, or start a session. It passes only when:

  • The sign-in comes from this organization's IdP connection.
  • Your IdP returns the same email as your Upbound account.
  • That email is on one of the organization's verified domains.

If the test fails, the SSO page tells you why:

ResultWhat to do
Wrong organizationThe sign-in came from another organization's IdP. Start the test from this organization's SSO page and check your connection settings.
Different accountYour IdP returned another email. Sign out of your IdP or switch accounts, then test again.
Domain not verifiedYour email domain isn't verified for this organization. Verify it in step 1, then test again.
Didn't completeTry again. Check that your IdP account has your work email and a first and last name.

Step 4: Review and turn on​

Before you turn SSO on, Upbound shows checks that must pass and a report of how SSO affects each member.

Checks

CheckPasses when
Identity provider connection is activeThe connection from step 2 is active.
Every member uses a verified domainEvery member's email is on a verified domain, or the member is Upbound support.
No member belongs to another SSO organizationNo member already belongs to another organization that uses SSO.
Pending invitesNo invites are pending, or you confirm Upbound deletes them.
You've tested sign-inYou passed step 3 with the current connection.

Turn on SSO stays unavailable until every check passes.

To clear a blocking member, either verify their email domain in step 1 or remove them from the organization. You can remove blocked members from the review step directly.

Who keeps access

The report lists every member with:

  • How they sign in after SSO turns on: Your identity provider, or Upbound support access for Upbound staff.
  • Whether they lose access, and why.
  • Which sign-in methods they can no longer use: password, GitHub or Google.

It also shows how many members Upbound signs out and which pending invitations it deletes. For Business Critical organizations with a connected directory, it shows which teams link to directory groups, which teams Upbound creates, and how many people directory sync adds.

When the checks pass, select Turn on SSO, confirm that Upbound signs everyone out, including you, and sign in again through your IdP.

Directory sync​

Business Critical Plan Feature

This is a Business Critical Plan feature. For more information, see our pricing plans or contact our sales team.

Directory sync keeps your organization's members and teams in step with your directory, such as Microsoft Entra ID, Okta or Google Workspace. You can connect a directory only after SSO is on.

To connect a directory, open the setup portal from the Directory sync section of the SSO page and follow the guide for your directory. For setup steps and screenshots for your directory provider, find it in the WorkOS integrations guides.

After you connect the directory:

  • Users join and leave with the directory. Adding a user in the directory adds them to the organization as a member. Removing a user from the directory removes them from the organization and its teams.
  • Groups become teams. Each directory group links to the Upbound team with the same name. If no team has that name, Upbound creates one. Group membership changes update the linked team.
  • The directory manages linked teams. You can't rename or delete a linked team or change its members in Upbound. Change the group in your directory instead.
  • The directory manages membership. You can't remove members from the organization in Upbound. Remove them from your directory instead.

Turn off SSO and get help​

Owners can't turn SSO off in the console. Only Upbound support can, so nobody can use a broken or compromised IdP connection to take over or lock out your organization. To turn SSO off, contact Upbound support.

When support turns SSO off:

  • Members can sign in again with the methods they used before SSO: a password, or social sign-in with GitHub or Google. Support can send a password reset email to members who don't have a password.
  • Teams are no longer linked to directory groups.
  • Upbound removes members' SSO sign-in links, unless they also belong to another SSO organization.

Your domains and IdP connection stay in place. An owner can turn SSO on again from the SSO page. If the IdP connection hasn't changed, the owner's earlier test sign-in still counts.

Contact Upbound support if you can't complete a step, a domain is already verified by another organization, or members can't sign in.

Rules and limits​

Domains

  • A verified domain belongs to one Upbound organization. If another organization already verified your domain, contact support.
  • Each subdomain needs its own verification. Verifying example.com doesn't cover eng.example.com.
  • Domains must match in full. A member signs in with SSO only when their email domain is one of the verified domains.
  • An organization can verify several domains.

Members and sign-in

  • A person can belong to only one organization that uses SSO.
  • Members of an organization that uses SSO can't reset an Upbound password.
  • If the IdP connection stops working while SSO is on, members can't sign in. Upbound doesn't fall back to passwords. Fix the connection in your IdP or contact support.
  • Without directory sync, removing someone in your IdP stops them signing in again, but doesn't remove them from the organization. Remove them from the organization's Members page.
  • Without directory sync, Upbound keeps SSO sessions short even when a member chooses to stay signed in. With directory sync, sessions can last longer, because removing someone in the directory also removes them from Upbound.

Test sign-in

  • Each owner who turns SSO on needs their own passing test sign-in.
  • A test sign-in stays valid while the IdP connection stays the same. If the connection changes, test again.
  • An owner whose email isn't on a verified domain can't pass the test. Ask an owner with an email on a verified domain to test and turn on SSO.

Directory sync

  • Directory users whose email isn't on a verified domain aren't added.
  • Deleting a group in your directory deletes its linked team in Upbound.
  • If a team with a group's name is already linked to another group, Upbound creates a team named after the group followed by the group's ID in parentheses.
  • A connected directory has no effect unless SSO is on and the organization is on Business Critical. The SSO page shows a warning when directory changes aren't applied.

Plan changes

  • If your organization moves to a plan without SSO, SSO stays on but its settings lock. Contact support to make changes.