Skip to main content
Connecting a client’s Google Workspace domain adds account and sign-in data to a Risk Assessment: which users have 2-step verification, which accounts look abandoned, and where sign-ins and failures come from.

Requirements

  • A Risk Assessment. External Assessments cannot connect cloud accounts.
  • A Google Workspace admin account with API access enabled. If you get an authorization or Admin_Policy_Enforced error while connecting, the Microsoft 365 and Google Workspace FAQ shows how to allow API access in the Google Admin console.

Connect Google Workspace

  1. Open the assessment and go to Setup > Connect Cloud.
  2. On the Google Workspace card, select Connect Google Workspace. To have the client’s admin do it, use the copy button next to it and send them the link.
  3. Sign in with the admin account and approve access.
Google Workspace connection card on the Connect Cloud step of a Telivy risk assessment
After connecting, the card header shows the connection status and last sync time. Its actions menu has Refetch now and Disconnect. If the card says “Google Workspace stopped syncing and needs to be reconnected”, select Reconnect Google Workspace and approve again.

Where to find the results

Results are on the assessment’s Cloud tab, under Google Workspace. If Microsoft 365 is also connected, switch provider at the top of the tab.

Summary

The summary card shows Total Accounts, Accounts without MFA, Total Failed Logins, and Orphaned Accounts.

Accounts Status

This table lists each account with its name, email, Sign-in Status, MFA Status, last login, and successful and failed logins. Select Show No MFA to list only the accounts where MFA is Not Enforced. Select Show All to go back to the full list.
Google Workspace Accounts Status table with MFA status for each user
Use this table to check that every account still belongs to someone who should have access. Former employees’ accounts that are still enabled are a common way in for attackers.

Login Status

The login section counts total, successful, and failed login events, maps sign-in locations colored by severity, and charts failed logins by user and login activity over time. Repeated failed logins on one account are often the first sign of password guessing or credential stuffing.