Let your team sign in to InfraNest using their Google Workspace accounts, instead of a separate InfraNest password. This is for InfraNest administrators on an Enterprise plan who manage company sign-in.
#Overview
- Sets up a sign-in connection that only accepts accounts from your own Google Workspace.
- Suspending or deleting someone in Google Workspace immediately stops them from signing in to InfraNest.
- Different from the everyday Sign in with Google that InfraNest offers everyone: that one accepts any Google account and can't add newcomers to your organization automatically.
- Takes about ten minutes, split between the Google Cloud console and InfraNest.
- You need to be able to create a project in your company's Google Cloud organization, and to be an administrator in InfraNest.
NoteGoogle does not send groups. Everyone who joins through this connection gets the same role you choose during setup — you change individual roles in InfraNest afterwards.
#Before you start
- Use a Google Cloud project that belongs to your Workspace. The setting that keeps outside Google accounts out (Internal) only exists for a project inside your company's Google Cloud organization. A project created while signed in with a personal Google account won't have it.
#Start in InfraNest
- Go to Settings → Sign-in and choose Set up single sign-on.
- Choose Google Workspace.
- At Email domain, check the domain InfraNest suggests. Verifying it is recommended, so people can type their work address on the InfraNest sign-in page and new people can join automatically. You can also choose Skip; your team then uses your organization's sign-in link, and new people join by invitation. If it isn't verified yet, InfraNest shows the DNS record to add — choose Add it for me if InfraNest already manages that DNS zone, or add the record yourself and choose Check now.
- At Create the app, choose Copy to copy the Redirect URL at the top of this step. Keep this tab open — you'll come back to it shortly.
#Set up the sign-in screen in Google Cloud
In a second tab, open the Google Cloud console and pick your project, or create one for InfraNest, inside your company's organization.
- Open the menu and go to Google Auth Platform → Branding. If Google hasn't been set up for this project yet, choose Get started.
- Fill in the form:
- App name:
InfraNest— your people see this name when they sign in. - User support email: an address your people can write to, such as your IT team's.
- Audience: Internal, so only accounts in your Workspace can sign in.
- Contact information: an address Google can write to about this project.
- App name:
- Agree to the Google API Services User Data Policy, and choose Create.
If Internal isn't offered, the project isn't inside your Workspace organization. Create the project again from your Workspace account, rather than choosing External — an external app lets any Google account reach the sign-in.
You don't need to add scopes under Data Access. InfraNest only asks Google for a person's name and email address, which every app may ask for.
#Create the OAuth client
- Go to Google Auth Platform → Clients and choose Create client.
- Fill in the form:
- Application type: Web application.
- Name:
InfraNest— only you see this name. - Authorized JavaScript origins: leave empty.
- Authorized redirect URIs: choose Add URI and paste the Redirect URL you copied from InfraNest.
- Choose Create.
- Copy the Client ID and the Client secret right away. Google shows the full secret only now; afterwards it shows only its last few characters.
#Finish the connection in InfraNest
- Back in the InfraNest tab, on the Create the app step, paste the Client ID and Client secret.
- There's nothing else to fill in — InfraNest reads everything else from Google itself.
#Test, choose who gets in, and switch on
- On the Try it step, choose Sign in with Google Workspace to test. A new tab opens at Google — sign in with your own Workspace account. When it works, the step turns green. A test is required before you can switch the connection on.
- On the Who gets in step, choose what happens when somebody new signs in:
- Add them straight away is pre-selected. New people join with the role under Role for new members, which starts at Member (read-only).
- Ask an admin makes each newcomer's sign-in a join request that an administrator approves.
- Do nothing means people still need an invitation.
- Choose Switch on. The connection's status should now read: Connected to Google Workspace · Email domain verified · Test sign-in passed · Switched on.
WarningA Google Workspace connection has no list of people assigned to the app — every active account in your Workspace can sign in, including shared accounts and contractors with a Workspace account. If that's broader than who should see your infrastructure, choose Ask an admin instead.
Your Workspace admin may be able to narrow this further in the Google Admin console, under Security → Access and data control → API controls, which can limit an app to some organizational units. We haven't confirmed how that setting treats an app that only signs people in.
Your team signs in from the normal InfraNest sign-in page: they type their work address and choose Continue with ….
#Tips
- People always start from the InfraNest sign-in page — there's no InfraNest tile to launch from Google.
- If you create a new client secret in Google Cloud, paste it into the connection under Credentials and claim names and choose Replace. Until you do, nobody can sign in through Google Workspace.
- If your Workspace has more than one email domain, verify each domain people sign in with.
- Google Workspace can't be used to confirm sensitive actions (like deletions) that require signing in again — Google offers no way to force a fresh sign-in, so people confirm with a passkey, an authenticator app or their password instead.
- Once sign-in works, you can require single sign-on for your whole organization under Settings → Sign-in. InfraNest asks for at least one owner with a passkey first, so a problem at Google can never lock you out.
#Troubleshooting
- Google shows "Error 400: redirect_uri_mismatch": the address under Authorized redirect URIs doesn't match the Redirect URL in InfraNest. Copy it again — it must match exactly, including
https://and any trailing slash. A change to the client can take a few minutes, sometimes longer, to apply at Google. - Google shows "Error 403: org_internal": the account used to sign in isn't in your Workspace. Sign in with a Workspace account, or check that the project belongs to the right organization.
- Google shows "Error 401: invalid_client": the Client ID in InfraNest is mistyped, or the client was deleted in Google Cloud.
- Someone signs in at Google but InfraNest doesn't let them in: their address isn't on a domain you verified in InfraNest.
- Administrators can see every failed attempt, with the reason, in Settings → Audit Log.
Was this article helpful?
Thanks for your feedback!
Thanks, this goes straight to the docs team.