Set up Okta SSO (and optional SCIM) for Hyperbound

Let your team sign in to Hyperbound with Okta using SAML 2.0. If you'd also like users added and removed from Okta automatically, you can turn on SCIM provisioning once single sign-on is working.

Time needed: about 30–60 minutes for SSO, plus about 30 minutes for SCIM. Who should do this: an Okta administrator who can create app integrations.

Before you start

• Get your setup link from Hyperbound. Your Hyperbound account team will send you a secure setup link that starts with https://auth.hyperbound.ai/setup_saml/. It's unique to your workspace and walks you through each step. Links expire, so if yours sends you to a login page or home page instead of the setup guide, ask your account team for a new one.

• Decide who should have access. Anyone you assign to the Hyperbound app in Okta can sign in. The first time they do, they're added to your Hyperbound workspace and count toward your licensed seats. Assign a specific Okta group rather than everyone.

• Check your email domains. Your Hyperbound workspace is linked to your company email domain. If some users sign in with a different domain (for example, one from an acquired company), tell your account team before you begin.

• Use the same email everywhere. Each user's Okta email should match the email they use in your call recording tools (Gong, Zoom, etc.), so their calls are matched to the right person in Hyperbound.

Part 1: Set up single sign-on

Step 1: Open the setup link and choose Okta

Open the setup link from Hyperbound and select Okta as your identity provider. Keep this tab open. You'll copy values from it into Okta and paste values from Okta back into it.

Step 2: Create the SAML app in Okta

1. In the Okta Admin Console, go to Applications → Applications and click Create App Integration.

2. Select SAML 2.0 and click Next.

3. Name the app Hyperbound and click Next.

4. In SAML Settings, copy these values from the Hyperbound setup guide:

   • Single sign-on URL

   • Audience URI (SP Entity ID)

5. Set Name ID format to EmailAddress and Application username to Email.

6. Under Attribute Statements, add the attributes the setup guide lists (email, first name and last name). Use the attribute names exactly as the guide shows them.

7. Click Next, choose I'm an Okta customer adding an internal app, and click Finish.

Step 3: Give Hyperbound your Okta details

1. In the new Hyperbound app in Okta, open the Sign On tab and click View SAML setup instructions.

2. Copy the values the Hyperbound setup guide asks for into the guide:

   • Identity Provider Single Sign-On URL

   • Identity Provider Issuer

   • X.509 Certificate

Tip: Copy each value into its matching field. The most common setup error is pasting the Issuer or the metadata URL into the Single Sign-On URL field.

Step 4: Assign users

On the app's Assignments tab, assign the users or groups who should have access to Hyperbound.

Step 5: Test the connection

In the setup guide, click Test Connection and sign in with an Okta user who is assigned to the Hyperbound app. The test user doesn't need a Hyperbound account yet.

Step 6: Go live

After a successful test, click Finish & Go Live in the setup guide.

Important: Until you click Finish & Go Live, the connection stays in test mode. Users who try to sign in will be asked for a password instead of being sent to Okta.

How your team signs in

• From Okta: click the Hyperbound tile on the Okta dashboard. Your Hyperbound account team can give you a direct sign-in link to use for the tile.

• From Hyperbound: go to app.hyperbound.ai, enter a work email, and you'll be sent to Okta to sign in.

Part 2: Set up SCIM provisioning (optional)

SCIM keeps Hyperbound in sync with Okta:

• Users assigned in Okta get a Hyperbound account automatically.

• Profile changes in Okta update Hyperbound.

• Users unassigned or deactivated in Okta are blocked from Hyperbound right away.

SCIM is available on request. Contact your Hyperbound account team to turn it on for your workspace. You can only set it up after single sign-on is live, so the SCIM step in the setup guide stays greyed out until then.

1. Return to the setup guide and open the SCIM section. It shows your SCIM base URL and API token. Store the token somewhere secure, because it gives access to your user directory.

2. In Okta, open the Hyperbound app and go to the General tab. Under App Settings, click Edit, set Provisioning to SCIM, and save.

3. On the Provisioning tab, go to Integration and click Edit. Paste the SCIM connector base URL and the API token from the setup guide, use Email as the unique identifier, and set the authentication mode to HTTP Header. Click Test Connector Configuration, then Save.

4. Under Provisioning → To App, click Edit and turn on Create Users, Update User Attributes and Deactivate Users. Save.

5. Optional: assign Hyperbound roles from Okta. The setup guide's role-mapping step shows how to add a role attribute. Role values are case-sensitive and must match exactly, for example Admin, not admin or ADMIN.

Check it's working

• Assign a test user in Okta. They should appear in Hyperbound within a few minutes.

• Unassign them. They should be blocked from Hyperbound and signed out.

Troubleshooting

If you're still stuck, reply in your shared Slack channel or email help@hyperbound.ai with a screenshot and the time you tried. We'll check our sign-in logs.