Google Workspace Integration
Set Up Google Workspace SSO for UnDesked
Before you start, you need:
- Access to Google Cloud Console with permission to create a project and OAuth credentials in your Workspace organization.
- An UnDesked admin account that can open Settings > Integrations.
- About 15 minutes in one sitting. The client secret is shown in full only when you create it, so keep it somewhere safe until you paste it into UnDesked.
Start in the same browser tab where you are signed in to UnDesked at app.undesked.com. Setup and the test step fail if you begin from an older bookmark such as app.lobbyfox.com or app.sendtransmission.com.
Production values
Copy these exactly. Both redirect URIs are required: if only the first is added, the test in UnDesked fails and the integration never turns on.
|
Setting in Google |
Value |
|---|---|
|
Application type |
Web application |
|
Authorized redirect URI 1 (user sign-in) |
|
|
Authorized redirect URI 2 (admin test) |
|
|
Authorized JavaScript origins |
Leave empty. Not needed. |
|
Scopes |
|
|
User type (Audience) |
Internal |
Enter each URI with https://, all lowercase, and no slash at the end. Google rejects any URI that differs by even one character.
Set up Google Cloud
Step 1: Create or pick a project
- Go to console.cloud.google.com and sign in with your Workspace admin account.
- In the project picker at the top, click New Project.
- Name it something clear, such as UnDesked SSO, choose your organization, and click Create.
- Make sure the new project is selected before you continue.
Step 2: Set up the consent screen
- Open the menu and go to APIs & Services > OAuth consent screen (in newer consoles this opens Google Auth Platform). Click Get started if prompted.
- Under App information, enter the app name UnDesked and a support email.
- Under Audience, choose Internal. This limits sign-in to accounts in your Workspace organization. Do not choose External (see Restricting access below).
- Add a contact email and finish the setup.
- Go to Data Access (or Scopes) and confirm
openid,emailandprofileare included. These are standard scopes and need no Google review.
Step 3: Create the OAuth client
- Go to Clients (or APIs & Services > Credentials) and click Create client (or Create credentials > OAuth client ID).
- Set Application type to Web application.
- Name it UnDesked Production.
- Leave Authorized JavaScript origins empty.
- Under Authorized redirect URIs, click Add URI twice and enter both values from the Production values table:
https://app.undesked.com/api/backend/login-oidc-callbackhttps://app.undesked.com/api/backend/authenticate-oidc
- Click Create.
Step 4: Copy the credentials
- Google shows the Client ID and Client secret. Copy both, or download the JSON file.
- Store the secret somewhere secure, such as your password manager. Google may not show it in full again.
Google notes that redirect URI changes can take a few minutes to take effect. If the test in the next section fails right away with a redirect error, wait five minutes and try again.
Connect it in UnDesked
Step 5: Enter the credentials
- Sign in to UnDesked at app.undesked.com as an organization admin.
- Go to Settings > Integrations and click Configure on the Google Workspace card.
- Paste the Client ID and Client Secret from Step 4. Both are required.
- Optional: choose default roles per location. These are the permissions given to anyone who signs in with Google and does not have an UnDesked account yet. People who already have an account keep their current permissions.
- Click Save.
Step 6: Test the integration
- Click Test Integration.
- A Google sign-in window opens. Sign in with your Workspace account and approve access.
- You return to UnDesked. A success message means the integration is now active.
The integration stays inactive until the test succeeds, so no one can sign in with Google until this step passes.
How people sign in
Share this sign-in link with your team, replacing the end with your location or organization identifier (shown on the integration card in UnDesked):
https://app.undesked.com/backend/login?identifier=YOUR-IDENTIFIER
People can also enter the identifier on the UnDesked login page. Then they pick their Google account and land in UnDesked.
What changes for them:
- Existing accounts are matched by email address. Their roles and history stay the same.
- New people get an UnDesked account on first sign-in, with the default roles you chose in Step 5.
- Passwords stop working. Once someone signs in with Google, they can no longer use their UnDesked password. Let your team know before you share the link.
- Signing out of UnDesked does not sign them out of Google. On shared devices, people should also sign out of their Google account.
Access, upkeep and troubleshooting
Restricting who can sign in
Google controls who can sign in. Keep the consent screen's user type set to Internal so only accounts in your Workspace organization get in. If it is set to External, any Google account, including personal Gmail, could sign in and receive the default roles.
To limit access further, for example to one department, restrict the app in your Google Admin console under Security > Access and data control > API controls.
Rotating the client secret
- In Google Cloud, open the OAuth client and add a new secret.
- In UnDesked, open the Google Workspace integration, paste the new secret, save, and run Test Integration again.
- Once the test passes, delete the old secret in Google.
Troubleshooting
|
What you see |
Likely cause |
Fix |
|---|---|---|
|
Google error: redirect_uri_mismatch |
A redirect URI is missing or mistyped |
Check both URIs against the Production values table: |
|
Test Integration fails, sign-in never turns on |
The admin test URI ( |
Add it in Google, wait five minutes, test again. |
|
Error 400 when starting sign-in or the test |
Started from an old address such as app.lobbyfox.com |
Open app.undesked.com in a fresh tab and start again. |
|
Google says the account is not allowed |
The user is outside your Workspace organization (Internal user type) |
Expected. Use an account in your organization. |
|
Sign-in rejected for one person |
Their Google email is not verified |
Have them verify their email in Google, or check their account in Google Admin. |
|
Someone can no longer use their password |
They signed in with Google once |
Expected. They sign in with Google from now on. |
Getting help
Email support@undesked.com or use the Support button at the bottom left of the UnDesked admin. Include a screenshot of any error and the time it happened.