TL;DR: Google single sign-on (SSO) lets your team sign in to BoldSign with the Google account they already use. You create an OAuth client in Google Cloud, paste its details into our SSO settings, and invite your users. Our eSignature for enterprise page shows where SSO fits with our other admin controls.
Your team already signs in to Gmail, Drive and Calendar with one Google account. A separate BoldSign password is one more thing to forget and one more account to close when someone leaves.
With SSO, Google handles the password and BoldSign trusts Google’s answer. This guide covers what Google SSO is, then walks through each screen in Google Cloud and in BoldSign.
What is Google SSO?
Google SSO is a way to sign in to many apps with one Google account. The app sends you to Google, and Google tells the app who you are.
Think of a staff badge at a large office. Security checks your face once at the front desk. After that, the badge opens every door you are cleared for.
Google sign in SSO works the same way, using the OAuth 2.0 and OpenID Connect (OIDC) standards. Google is the identity provider (IdP), the front desk. BoldSign is one of the doors.
Why use SSO with Google for BoldSign?
SSO with Google gives your users one less password and gives admins one place to control access. Each benefit comes from Google holding the sign-in.
- Users sign in with the Google account they open every day.
- Turn off someone’s Google account and their SSO Google login stops too.
- Your Google security rules, such as two-step checks, apply to BoldSign sign-in.
- New staff join from an email invite with no new password to create.
BoldSign SSO works with any provider that supports OAuth or OpenID. We also have guides for Auth0 and OneLogin.
How to set up Google SSO for BoldSign
The Google SSO setup has three parts. You build an OAuth client in Google Cloud, enter its details in BoldSign, then invite your users.
Setting up Google SSO needs two admin roles: the person who manages your Google Cloud project and a BoldSign account administrator. One person can hold both.
Google Cloud console is the admin site for Google Cloud Platform (GCP). Most of the Google console SSO work happens on two pages: the OAuth consent screen and Credentials.
Step 1: Create a project in Google Cloud console
- Go to Google Cloud Console and sign in with your Google account.
- Select the project picker at the top, which shows My First Project on a new account.
- Select New Project in the dialog box.
- Name your project and select Create.
A Google Workspace account suits an organization, because the Workspace admin controls every user. A personal Google account works for a test.
Step 2: Set up the OAuth consent screen
- Go to APIs & Services, then OAuth consent screen.
- Enter the app name and a user support email.
- Choose Internal for Workspace users only, or External for any Google account.
- Add your contact information and save.
For a Google Workspace SSO setup, choose Internal. Only accounts in your Workspace domain can then sign in.
Step 3: Create the Google SSO app credentials
Google needs a redirect uniform resource identifier (URI): the address it sends users back to after sign-in. BoldSign gives you that address.
- In BoldSign, go to Settings, then Identity Management, and copy the Redirect URL under Single Sign-On.
- In Google Cloud, go to APIs & Services, then Credentials, then Create Credentials, then OAuth client ID.
- Select Web application as the application type.
- Paste the BoldSign Redirect URL under Authorized redirect URIs, then save.
- Copy the Client ID and Client Secret that Google shows.
The Client ID works as your Google SSO ID, and the secret proves the request comes from you.
Step 4: Add test users for an External app
Skip this step when you chose Internal. An External app in testing only lets in the accounts you list.
Go to APIs & Services, then OAuth consent screen, then Audience. Under Test users, select Add users and enter each user’s email address.
How do you enter the Google SSO configuration in BoldSign?
Open the Single Sign-On section in BoldSign, choose OAuth, and fill in five fields. Only an account administrator can reach this page.
- Log in to BoldSign and go to Settings, then Identity Management.
- Under Single Sign-On, choose OAuth as the method.
- Paste the Client Id and Client Secret from Google Cloud.
- Fill in the three endpoint fields with the addresses listed below.
- Select Save.
Google lists these addresses in its OpenID discovery document:
- Token Endpoint:
https://oauth2.googleapis.com/token - Authorization Endpoint:
https://accounts.google.com/o/oauth2/v2/auth - User Information Endpoint:
https://openidconnect.googleapis.com/v1/userinfo
How do you invite users to sign in with Google SSO?
Invite each person from Users & Teams, using the same email as their Google account. They join through the email and sign in with Google.
- Go to Users & Teams, then Users, and select Invite users.
- Enter one or more email addresses, select Add, then select Invite.
- The user opens the invitation email and selects its link.
What does the new user see?
The link opens our sign-in page with a button that names your organization. The user selects it and signs in on Google’s page.
Next, they choose Yes, Keep me signed in or No. On the Basic Info page, they add their name and phone number and select Proceed.
How does Google SSO login work for your users?
Each login with Google SSO starts on the BoldSign login page. Users never open the console: the GCP SSO login and Google Cloud SSO login settings are for the admin only.
In each SSO login Google checks the password and sends the user back to BoldSign.
- Go to the BoldSign login page and select Sign In with SSO.
- In Organization Email, enter the SSO Gmail or Workspace address you were invited with.
- Select Continue, then finish the Google SSO sign in on Google’s page.
- Choose Yes to stay signed in for 30 days, or No.
Users then land on the BoldSign dashboard, so there is no separate Google SSO dashboard to learn.
Which Google SSO account can you use?
Google account SSO works with Google Workspace accounts and personal Gmail accounts. The account must match the email address you invited.
- Each user needs an SSO Google account that your OAuth client accepts.
- Workspace accounts should sit in your organization’s domain, under your admin console.
- Gmail personal SSO is fine for testing, but use Workspace accounts for your team.
Check that you sign in with Google single sign on official website pages only. The Google page address should start with accounts.google.com.
What should you watch out for?
Most problems come from a field that does not match. Check these before you invite the whole team.
- Google SSO connections work only for users you have invited to your BoldSign organization.
- Choose OAuth in BoldSign, since the Google endpoints above are OAuth fields.
- The Redirect URL in Google Cloud must match BoldSign’s exactly.
- An External app in testing lets in listed test users only.
Selecting Delete SSO at the bottom of the SSO page turns SSO off for everyone. Our help article on how to delete the SSO configuration shows each step.
Which BoldSign plan includes SSO, and what does it cost?
Single sign-on starts on the Business plan, as listed on the BoldSign pricing page in November 2026. The Essential and Growth plans do not include it.
The Business plan costs $15 per user a month, and the Premium plan costs $99 a month for unlimited users. Both are billed yearly.
The Enterprise API plan also includes SSO and starts at $30 a month with 40 envelopes. Prices are in USD.
Where do you go next with Google SSO?
Try the whole Google single sign on setup with one test user before you roll it out. Then invite the rest of your team.
- Start a 30-day free trial and look around our features.
- Book a demo to see SSO set up for your organization.
- Open a support ticket if a sign-in step fails.
Frequently asked questions
Is Sign in with Google SSO?
Yes. Sign in with Google is a form of single sign-on: one Google account opens many apps. Google checks the password, and each app trusts that answer.
Can I use the same steps to add Google SSO for my application?
Yes, for the Google part. Any app that supports OAuth 2.0 or OpenID Connect (OIDC) needs the same client ID, client secret and redirect URL from Google Cloud.
How to add Google SSO to my website?
Create an OAuth client ID for a web application in Google Cloud and add your site's callback address as a redirect URL. Then give the client ID and secret to your site's sign-in code.
Should I use SSO Google Workspace accounts or personal Gmail accounts?
Use Google Workspace accounts for your team. Your Workspace admin then decides who can sign in. Gmail SSO with a personal account is fine for a test.
Who can set up SSO in BoldSign?
Only an account administrator can open the SSO settings. Other users join by invite and then sign in with their Google account.
How long does BoldSign keep me signed in after an SSO login?
Select Yes on the stay signed in page and we keep you signed in for 30 days. Select No to sign in again next time.
What happens if I delete the SSO configuration?
SSO stops for everyone in your organization. Users need another way to sign in until an administrator sets SSO up again.
Which BoldSign plan includes single sign-on?
Single sign-on comes with the Business, Premium and Enterprise API plans. The Essential and Growth plans do not include it.