Somebody hands you the keys to a Google Workspace tenant and expects you to know what to do with them. The first week is usually a blur of half-finished settings pages, a support ticket about mail that never arrived, and a vague warning that the previous admin „had it set up a certain way.” Before you touch a single routing rule, the job is to establish what you actually control, what already exists, and how to prove a change worked. That is the whole thesis of this checklist: verify access, lock it down, write down the inventory, then test before you configure. The order matters because each step depends on the one before it.<\/p>\n
Google Workspace catch-all email is a good example of why sequence counts. Catch-all routing looks like a one-line fix for misaddressed email, but it lives inside the Admin console behind the Gmail Settings administrator privilege, and it only fires when the „All inactive and unrecognized accounts” option is ticked in the routing rule. Get that wrong and you will spend an afternoon wondering why mail to a typo address still bounces. Get it right and you have a safety net for inbound messages, with catch-all limits you should understand before you promise anyone anything.<\/p>\n
The first three moves are 2FA, an alias and group inventory, and Email Log Search. None of them are glamorous. All of them prevent the kind of incident that gets a new admin’s access reviewed by someone else. Work through the checklist in order and keep notes as you go, because the register you build now is the reference you will reach for every time a user says the mail went missing.<\/p>\n
The first thing a new Google Workspace administrator should check is not a setting but an identity: their own. Log into the Google Workspace Admin console and confirm the account you are using holds the super admin role. Open Admin console > Account > Admin roles and look at the list of users assigned to the Super Admin role. If your name is not on it, you are working from a delegated account, and some of the settings you plan to touch will be invisible or read-only. Editing routing from a partial-privilege account is how mail quietly stops flowing while the console shows no error.<\/p>\n
Super admin access is only half the check. The other half is recovery: if the super admin account is locked out, who gets back in? Work through the following before you edit anything.<\/p>\n
The account inventory matters because aliases, Groups, and delegated mailboxes all resolve to real accounts. If you do not know which accounts exist, you cannot predict where a catch-all routing rule will send mail. The entity relationship is simple: Google Workspace implements catch-all via routing rules in the Admin console, and a catch-all routing rule redirects mail to a user account or Google Group. Point that rule at an account nobody monitors and inbound messages vanish without a bounce.<\/p>\n
Two more checks belong here. First, confirm you can sign in to the Admin console from a clean browser profile, not a saved session that may belong to a former admin. Second, note that Google states changes may take up to 24 hours to apply, so a setting that looks wrong today may simply be propagating. Do not „fix” it twice.<\/p>\n
Only after the super admin role and recovery paths are confirmed should you move on to access hardening. Everything else in this checklist assumes you can undo your own changes.<\/p>\n
Before you touch a single routing rule, lock the doors. A compromised admin account can rewrite where every inbound message lands, so two-step verification comes before configuration work, not after it. Google Workspace makes this straightforward, but the defaults do not protect you on their own.<\/p>\n
Start by turning on two-step verification enforcement for the whole organization, then tighten it for privileged accounts. In the Google Workspace Admin console, go to Security > Authentication > 2-step verification and set enforcement to On for the top organizational unit. New users get a grace period to enroll; set that window to something short, seven days or less. For super admins and anyone with the Gmail Settings administrator privilege, consider a stricter policy: security keys only, no SMS fallback. SMS is the weakest second factor and SIM swaps are routine.<\/p>\n
Next, audit recovery methods. Open each admin account and confirm the recovery phone and recovery email are current and controlled by your organization, not by a personal address the admin set up years ago. Remove stale phone numbers. Add a second super admin as a break-glass account with credentials stored in a password manager the team controls, and make sure at least two people can reach it. A single super admin with an outdated recovery phone is one lost device away from a locked tenant.<\/p>\n
Then write down who holds privileged roles. Export the list of users with admin roles from the Admin console and record it in a shared document with three columns: name, role, date granted. Include delegated admin roles, not just super admins. Review the list quarterly and remove access the moment someone changes teams. Undocumented privileged accounts are the ones that get forgotten, and forgotten accounts are the ones that get compromised.<\/p>\n
Finally, verify enforcement actually took effect. Sign in from a fresh browser as a test admin account and confirm you are prompted for the second factor. Check the security report for users who have not enrolled and follow up individually. Google states changes may take up to 24 hours to apply, so do not assume a quiet dashboard means the policy is live.<\/p>\n
Do this before any catch-all email setup or routing rule work. If routing goes wrong later, you want to know that only verified, documented people could have caused it.<\/p>\n