Google Workspace security checklist: what to check in the Admin console
The checks that catch most account risk in a small Google Workspace domain are: every admin, and ideally every user, enrolled in 2-step verification; more than one super admin, each held by a different person and not used for daily work; admin roles only where they are needed; third-party apps reviewed; automatic forwarding to outside addresses switched off or explained; strong passwords; and recovery options on every admin account. Each check takes minutes in the Admin console, and most of the facts sit in one place, the Accounts report under Reporting > User reports, which shows for every account its 2-step verification enrollment, password strength and the number of external apps it has connected. Google's own security checklist for small businesses is the source for most of what follows.
The checklist at a glance
| # | Check | Where in the Admin console |
|---|---|---|
| 1 | Admins and users enrolled in 2-step verification | Reporting > User reports > Accounts; enforce under Security > Authentication > 2-step verification |
| 2 | More than one super admin, each a different person | Account > Admin roles, Super Admin, view the admins |
| 3 | Super admin accounts not used for daily work, and still working | Directory > Users, last sign-in of each super admin |
| 4 | Admin roles only where needed | Account > Admin roles |
| 5 | Third-party apps reviewed | Accounts report, External apps; Security > Access and data control > API controls |
| 6 | No unexplained forwarding outside the domain | Apps > Google Workspace > Gmail > End User Access; Reporting > Audit and investigation > User log events |
| 7 | Strong passwords | Accounts report, Password strength; Security > Authentication > Password management |
| 8 | Recovery options and backup codes on admin accounts | Each admin's own account |
1. 2-step verification, for admins first
A stolen password is enough to take over an account without 2-step verification (2SV). Google's checklist recommends 2SV for everyone and says to enforce it for admins and for users who handle sensitive data such as finances or employee records, and Google states that it is enforcing 2SV for administrator accounts itself.
- Check: the Accounts report has the columns 2-Step Verification enrollment and 2-Step Verification enforcement for every account. Export it and sort.
- Fix: as a super admin, open Security > Authentication > 2-step verification, allow users to turn it on, give them time to enroll, then enforce it for an organisational unit or a group. New users can get an enrollment period of 1 day to 6 months, during which a password alone still works. Security keys are the strongest method; you can require them for admins.
2. More than one super admin
If your only super admin loses their phone, leaves, or has the account compromised, nobody can manage the domain until Google's account recovery is done. Google is explicit: an organisation "should have more than one super administrator account, each managed by a separate person". A shared login doesn't count: give each admin their own account, so the logs show who did what.
- Check: Account > Admin roles, open Super Admin and view the admins assigned to it.
- Fix: give a second, trusted person super admin rights on their own account. Keep the account information and DNS access Google asks for in a recovery to hand, in a safe place.
3. Super admins: not for daily work, but not forgotten
Google recommends a separate, non-admin account for each super admin's everyday work, signing in to the super admin account only for super admin tasks, and not staying signed in. The other side of that advice: a backup super admin nobody has signed in to for months may not work on the day you need it.
- Check: in Directory > Users, look at the Last sign in of each super admin.
- Fix: sign in to a long-unused super admin account and confirm its 2-step verification and recovery options still work; delegate daily admin tasks to accounts with limited admin roles.
4. Admin roles only where they are needed
Every admin account is a bigger target than a user account. Google recommends least privilege: give someone the limited role they need, such as resetting passwords, rather than super admin.
- Check: Account > Admin roles lists each role and who holds it. Note anyone who became an admin since your last check.
- Fix: remove roles nobody uses; replace super admin with a narrower role where it will do.
5. Third-party apps with access to your data
When someone signs in to an outside app with their Workspace account, the app can be given access to their mail, files or calendar. Most are harmless; a few should not be there.
- Check: the External apps column of the Accounts report counts the non-Google apps for each account; the user's own page, under Security, names them.
- Fix: under Security > Access and data control > API controls, open Manage Third-Party App Access. You can mark each app Trusted, Limited, Specific Google data or Blocked, and restrict Google services so that only apps you have allowed can reach them. Restricting a service revokes the tokens of apps you haven't trusted.
6. Mail forwarded outside the domain
A forwarding rule to a private or unknown address copies every new message out of your organisation, silently, often long after anyone remembers setting it up. Unexpected outside forwarding is also a common sign of a compromised account.
- Check: in Reporting > Audit and investigation > User log events, look for out-of-domain email forwarding events, which Google logs when an account turns on forwarding to an outside address ("has enabled out of domain email forwarding to" the destination). Every edition can search these logs with the audit and investigation tool.
- Fix: under Apps > Google Workspace > Gmail > End User Access > Automatic forwarding, choose whether users may forward automatically, and if so to any address or to internal addresses only. The option is on by default, and it can differ per organisational unit.
7. Strong passwords
2-step verification covers a weak password; a weak password without it is the easiest way in.
- Check: the Accounts report shows Password strength and Password length compliance per account.
- Fix: under Security > Authentication > Password management, enforce strong passwords and a minimum length (8 to 100 characters). It needs the Security settings privilege. Google keeps password expiry off by default, because research shows it does little for security.
8. Recovery options and backup codes for admins
Google's checklist asks admins to add a recovery phone number and email, and admins and users with 2SV to print backup codes and keep them somewhere safe. Admins with security keys should enroll a spare one. Without them, a lost phone can lock a super admin out.
How often to run it
Once a month takes a quarter of an hour, and two moments need it at once: when someone becomes an admin, and when someone leaves. A leaver's account keeps its authorised apps and forwarding rules until you act (deleting a user lists the steps). Doing it by hand means joining the Accounts report, the admin roles page and the audit log yourself each time.
WorkspaceRadar's scan reads the same Google reports and lists admin accounts without 2-step verification, a domain only one account can administer, a super admin with no sign-in for 90 days, weak passwords, third-party apps people have authorised, and mail forwarded to addresses outside your domain, each with the step to take in the Admin console. It changes no security setting itself; the same scan finds the unused licenses and what they cost.
Check your domain for these security gaps, free
WorkspaceRadar changes nothing without your approval of that specific change, and asks for no email and no card.
Questions
Is 2-step verification mandatory for Google Workspace admins? Google states that it is enforcing 2-step verification for administrator accounts. For everyone else it is your setting: enforce it under Security > Authentication > 2-step verification.
How many super admins should a Google Workspace domain have? More than one, each managed by a separate person, Google says, without naming a number. Two people you trust is the usual minimum for a small organisation.
Can I stop users forwarding email to outside addresses? Yes. Under Gmail > End User Access > Automatic forwarding, turn automatic forwarding off, or allow it to internal addresses only. It is on by default.
Where do I see which third-party apps have access to our data? Under Security > Access and data control > API controls > Manage Third-Party App Access for the domain, and on each user's page under Security for the apps that account has connected.
Which report shows 2-step verification and password strength for every user? Reporting > User reports > Accounts. It needs the Reports administrator privilege.
Is there an official Google Workspace security checklist? Yes: Google publishes one for small businesses (1 to 100 users) and one for medium and large businesses; organisations with special regulatory requirements should follow the second.
Sources: Google Workspace Admin Help, Security checklist for small businesses (1-100 users), Security best practices for administrator accounts, Deploy 2-Step Verification, User reports: Accounts, Control which apps access Google Workspace data, Let users automatically forward their own Gmail emails, User log events and Enforce and monitor password requirements for users; Google Workspace Admin SDK, Login activity events.