Google Workspace administrators control which outside apps their staff are allowed to sign in to. Before your team can sign in to Teammate with Google, your Workspace administrator needs to trust Teammate in the Google Admin console — a few clicks, done once for your whole organisation. Teammate then tests the connection and turns Google sign-in on.
Before you start
Single Sign-On has to be switched on for your company first. If you don’t see a Single Sign-On connections section under System Administration → General, email support@teammateapp.com and we’ll turn it on.
Open the Connect box
- Go to System Administration → General.
- Find the Single Sign-On connections section. The Google Workspace card shows Not activated yet until it’s trusted.
- Click Connect Google. The Activate Google sign-in box opens with the steps below already listed, ready to copy or email.
What your Workspace administrator does
- Open the Google Admin console → Security → Access and data control → API controls → Manage App Access.
- Choose Add app → OAuth App Name or Client ID, search for each of the three IDs below, tick them and select them.
- Set access to Trusted (or Limited — Teammate only asks for sign-in information) and save.
- Back in Teammate, click Test and activate.
The three client IDs
There are three because Teammate’s web app and its two mobile apps are separate Google clients. All three need to be added, or sign-in will only work on some of them.
| Client ID | App |
|---|---|
| 43995030076-tai9aat9t58r2u1tfne44gcj0b6o5cjt.apps.googleusercontent.com | Teammate web |
| 143086159247-1fp6rcqcslof3ui00dgsrtan55mbf5re.apps.googleusercontent.com | Teammate mobile |
| 143086159247-8iru422kejc2vprvik65obh7ufddgc3r.apps.googleusercontent.com | Teammate iOS |
Trusted vs Limited
Trusted and Limited are Google’s own access levels for apps that only ask for basic sign-in information, which is all Teammate requests. Either works for Teammate — pick whichever fits your organisation’s policy.
Test and activate
Once the three IDs are trusted, click Test and activate in Teammate and sign in with a Google account from your Workspace. If Google lets the sign-in through, Teammate records the connection immediately and the Google Workspace card switches to Connected — there is no separate approval step like Microsoft’s.
Signing in with a personal Gmail address
Teammate records the connection against your organisation’s Google Workspace domain. A personal @gmail.com address doesn’t have one, so testing with a personal account doesn’t activate anything — Teammate tells you that was a personal Google account and asks you to sign in with your work Google account instead.
Where else you’ll see this
Until Google is connected, anywhere a Login Type is chosen — the Add Employee wizard, an employee’s Credentials, or HR Admin → User Access Setting — shows an amber Not activated yet badge with an Activate it in System Administration link. Selecting Google sign-in there is still possible, but saving is refused until the connection above is made.
The SSO only switch
Below the two cards is an SSO only switch. Turning it on removes the Username option when adding or editing users, so every new login must be Microsoft or Google. It shows how many people currently sign in with a username, and existing username users keep signing in exactly as before — the switch only changes what’s offered when adding or editing someone.
Troubleshooting
Was this helpful?