Set up Google Workspace SSO for Hyperbound
Last updated: October 20, 2026
Let your team sign in to Hyperbound with their Google Workspace accounts using SAML 2.0. (This is single sign-on. To connect Gmail and Google Calendar instead, see Google Workspace.)
Time | About 30–60 minutes |
Who | A Google Workspace super admin, or an admin who can manage web and mobile apps |
You'll need | Your Hyperbound setup link (your account team sends it) |
Before you start
Get your setup link. Your Hyperbound account team sends a secure link that starts with
https://auth.hyperbound.ai/setup_saml/. It's unique to your workspace and shows the exact values you'll copy. Links expire, so if yours opens a sign-in or home page, ask for a new one.Decide who gets access. Anyone you assign to the Hyperbound app in Google can sign in, and is added to your workspace (and counts toward your licensed seats) the first time they do. Assign a specific group, not everyone.
Check your email domains. Your workspace is linked to your company's email domain. If some people use another domain, for example from an acquired company, tell your account team before you start.
Use one email everywhere. People are matched by email, so each person's email should be the same one they use in your call recorders (Gong, Zoom and others).
Part 1: Set up single sign-on
Step 1: Open your setup link
Open the link from your account team and choose Google. Keep the tab open: you'll copy values from it into Google, and paste values from Google back into it.
Step 2: Create the Hyperbound app in Google Workspace
In the Google Admin console, go to Apps → Web and mobile apps. Click Add app, then Add custom SAML app.
Name it
Hyperboundand click Continue.Leave the Google Identity Provider details page open: you'll use it in Step 3. Click Continue when you've copied its values.
Under Service provider details, fill in these fields and click Continue:
Google field
Value
ACS URL
Single sign-on URL from your setup guide
Entity ID
Audience URI / SP Entity ID from your setup guide
Name ID format
EMAILName ID
Basic Information › Primary email
Under Attribute mapping, add these and click Finish:
Google Directory attribute
App attribute
Primary email
emailFirst name
first_nameLast name
last_name
Step 3: Give Hyperbound your Google details
From the Google Identity Provider details page, copy each value into its own field in your setup guide:
Copy from Google | Paste into the setup guide |
|---|---|
SSO URL | Single sign-on URL |
Entity ID | Issuer / Entity ID |
Certificate | Certificate |
Most common mistake: mixing up direction. Google's SSO URL, Entity ID and certificate go into Hyperbound. Hyperbound's ACS URL and Entity ID go into Google.
Step 4: Assign people
Open the Hyperbound app, click User access, and turn it ON for the group or organizational unit that should use Hyperbound. New custom apps start OFF for everyone, and changes can take a little while to apply.
Step 5: Test the connection
In your setup guide, click Test Connection and sign in as someone who's assigned to the app. They don't need a Hyperbound account yet.
Step 6: Go live
When the test succeeds, click Finish & Go Live in your setup guide.
Don't skip this step. Until you click Finish & Go Live, the connection stays in test mode, and people are asked for a password instead of being sent to Google.
How your team signs in
From Google: open Hyperbound from the Google apps menu.
From Hyperbound: go to app.hyperbound.ai, type your work email, and you're sent to Google to sign in. Type the email rather than clicking a Google sign-in button: that's a separate sign-in method and won't use your company's single sign-on setup.
Adding people later: assign them in Google. They don't need an invitation from Hyperbound, and email invitations shouldn't be sent to people who sign in with single sign-on.
Roles and removing people
Accounts: a custom SAML app in Google Workspace doesn't create accounts ahead of time. Each person's account is created the first time they sign in.
Roles: everyone starts as Member. Admins change roles in Hyperbound.
Removing someone: suspending or deleting them in Google stops them signing in. Also remove them in Hyperbound to free their seat. If you need automatic provisioning, ask your account team about the options.
Troubleshooting
What you see | What to do |
|---|---|
The setup link opens a sign-in or home page | The link expired, or wasn't copied in full. Ask your account team for a new one. |
People are asked for a password instead of being sent to Google | The connection is still in test mode. Open the setup link and click Finish & Go Live. |
Test Connection fails after signing in | Re-check Step 3. The sign-on URL, issuer and certificate must each be in their own field, and the certificate must be current and complete, including its |
Google says the person isn't assigned to the app | Assign them, or a group they're in, to the Hyperbound app in Google. |
Someone has the wrong role | Google doesn't send roles. An admin changes the person's role in Hyperbound. |
Single sign-on suddenly stops working | Your Google signing certificate was renewed or expired. Ask your account team for a setup link and enter the new certificate. |
Someone can't reach Google from the Hyperbound sign-in page | Make sure they typed their work email instead of clicking a Google sign-in button, and that the app is turned on for their group or organizational unit. |
Google says the app isn't configured for the user | Turn the app on under User access for their group or organizational unit, then try again after a few minutes. |
Still stuck?
Reply in your shared Slack channel or email help@hyperbound.ai with a screenshot, the email of the person who tried to sign in, and the time they tried. We'll check our sign-in logs for that attempt.