Ask ten new Google Workspace administrators where to configure a Google Workspace catch-all email address and most will click into Users, then Domains, and come up empty. The instinct is understandable. Plenty of mail platforms put catch-all routing right next to mailbox management, so beginners carry that mental model into the Google Workspace Admin console and expect a toggle labeled “catch-all” somewhere near the user list. It is not there. Google Workspace lacks a dedicated catch-all switch entirely, and the feature is built from a general-purpose routing rule instead.
That single fact explains a lot of wasted afternoons. The catch-all email setup lives under Apps > Google Workspace > Gmail > Routing, inside what the interface calls the Gmail Settings area, not under Users or Domains. From there, an administrator creates a routing rule that applies to inactive and unrecognized accounts, uses the Change envelope recipient action to replace the recipient with a real destination, and lets Google deliver the message to a user account or a Google Group address. The rule fires on inbound messages addressed to names that do not exist on your domain, which is exactly the misaddressed email problem a catch-all mailbox is meant to absorb.
Two things trip people up before they even reach that screen. First, the Admin console search bar only returns results your privilege level allows, so a delegated admin can type “routing” and see nothing while the super admin sees the full menu. Second, the setting genuinely is not in Users, so no amount of scrolling will reveal it. Once you know the path, the rest is mechanics: pick the destination, confirm the rule covers the right accounts, and remember that changes can take up to 24 hours to apply.
Why New Admins Look for Catch-All in the Wrong Place
Open the Google Workspace Admin console for the first time and the left-hand menu looks like a filing cabinet with too many drawers. Users sits near the top. Domains sits under Account. Both feel like the obvious homes for a catch-all address, because on plenty of other mail platforms that is exactly where the catch-all switch lives. That instinct is the first thing to unlearn. Google Workspace lacks a dedicated catch-all switch in either of those menus, and no amount of clicking through Users or Domains will reveal one.
The confusion is understandable. On a traditional cPanel or Plesk server, catch-all is a per-domain toggle listed right beside the mailbox list. On Microsoft 365, administrators build transport rules that look like they belong with user management. Google’s design is different. Mail handling is treated as a routing concern, not an account concern, so the relevant controls live under Apps > Google Workspace > Gmail > Routing. An administrator looking at the Users list is browsing identities. The catch-all logic lives in the pipeline that decides where a message goes after it arrives.
Here is what beginners typically do instead. They open Users, scan for a setting called catch-all, find nothing, and assume the feature is missing or requires an upgrade. They check Domains and look for per-domain mail options, again finding nothing. Some go looking in the Admin console search bar, typing “catch-all” and getting results that point at unrelated Gmail settings. The search bar itself can deepen the confusion, because it only surfaces menus the signed-in account has privilege to see. A delegated admin without the Gmail Settings administrator privilege may search for routing and get nothing back, concluding the setting does not exist when in fact it exists and is simply hidden from that role.
Two facts reframe the whole search. First, Google does not sell catch-all as a standalone feature. It is assembled from a routing rule that uses the Change envelope recipient action to replace the recipient on inbound messages addressed to inactive and unrecognized accounts. Second, the destination is not a special mailbox type. Google allows a regular user account or a Google Group address to receive the redirected mail, which is why nothing in the interface is labeled “catch-all mailbox.”
That mismatch between expectation and interface explains why so many new admins spend an afternoon in the wrong drawer. The fix is not more patience with the Users page. It is knowing that catch-all is a routing configuration, that the rule applies to non-existent addresses rather than to real users, and that the privilege level of the signed-in account determines whether the relevant menus appear at all. Once that mental model shifts, the navigation path in the next section takes about thirty seconds to follow.
The Real Path: Apps > Google Workspace > Gmail > Routing
The path is short once you know it, and it does not pass through Users. Sign in to the Google Workspace Admin console at admin.google.com, open the left-hand menu, and go to Apps > Google Workspace > Gmail. In the Gmail settings pane, click Routing (some tenants label the same area Default routing). That screen is where catch-all logic lives, not under Directory > Users and not under Account > Domains. Users is for creating, suspending, and licensing accounts. Domains is for adding and verifying domain names. Neither one has a switch that says “catch all” because Google Workspace lacks a dedicated catch-all switch by design. You build the behavior yourself with a routing rule.
Why the Search Bar Sends Delegated Admins in Circles
Here is the part that trips people up. The Admin console search bar at the top is privilege-aware. It only returns results for settings the signed-in account can actually open. A super admin types “routing” and sees Gmail routing near the top. A delegated admin with Gmail privileges but without the right role types the same words and gets nothing useful, or gets a result that bounces them back to a permission error. The menu item itself may be missing from the left nav.
That is not a bug and not a broken tenant. The administrator role requires Gmail Settings administrator privilege to open and save routing rules. If the Routing page is absent, check the account’s admin roles before you assume the setting was moved or removed. Ask a super admin to grant the Gmail Settings administrator privilege, or to make the change on your behalf. This single check resolves a large share of “the catch-all option disappeared” tickets.
A practical note on timing: the console search index is not instant. After a role change is granted, allow a few minutes and reload the page before you conclude the privilege did not apply. Changes to routing rules themselves can take up to 24 hours to apply across the domain, so a rule that looks saved but does nothing yet is usually propagation, not failure.
For reference, here is where catch-all is and is not:
| Admin console area | What it controls | Catch-all here? |
|---|---|---|
| Directory > Users | Accounts, licenses, suspension | No |
| Account > Domains | Domain verification, aliases | No |
| Apps > Google Workspace > Gmail > Routing | Recipient mapping, envelope changes | Yes |
| Apps > Google Workspace > Gmail > Compliance | Content rules, blocking | No |
One more navigation fact worth internalizing: the destination of a catch-all rule can be a regular user account or a Google Group address. Google allows either as the recipient. A Google Group is often the better target because it accepts mail for non-existent addresses without consuming a paid user license, and it gives you a shared inbox several people can watch. Whichever you pick, the rule that does the work uses the Change envelope recipient action, which rewrites where the message is delivered while leaving the original To header intact. That distinction matters later when you test, because the message will still show the misaddressed email in its header even though it landed in the catch-all mailbox.
Bookmark the Gmail Routing URL directly. catch-all routing in Google Workspace provides further background on the subject. Two clicks saved per visit adds up when you are iterating on rules.
Reading the Routing Screen: Recipient Mapping and Catch-All Setup
When you land on Gmail routing, the first thing to understand is that this screen does not have a checkbox labeled “catch-all.” Google Workspace lacks a dedicated catch-all switch, so what you get instead is a general-purpose rule engine. Each entry in the list is a routing configuration that matches inbound messages on criteria you define, then applies one or more actions to them. The catch-all is something you build out of those parts, not something you turn on.
What the screen gives you: recipient mapping and message actions
The core controls fall into two groups. The first is recipient mapping. Under “Envelope recipient,” you can choose to change the envelope recipient on matched messages, which is the mechanism a catch-all rule relies on. The “Change envelope recipient” action lets you replace the recipient with a single address, and Google allows a user account or Google Group as that destination. You also get “Add more recipients,” which delivers a copy to additional addresses without altering the original, and “Reject message” for traffic you want refused outright.
The second group is message-level action. You can modify headers, prepend a subject tag, route through an alternate delivery path, or apply a quarantine, all in the same rule. For catch-all purposes you will mostly ignore these; the envelope recipient change is the working part. Note that a rule built here applies to inactive and unrecognized accounts, which is exactly the traffic a catch-all is meant to capture: mail addressed to people who never had a mailbox, or had one that was deleted.
Configuration steps, in order:
- In the Google Workspace Admin console, go to Apps > Google Workspace > Gmail > Routing. The equivalent entry point is the Gmail Settings area labeled “Default routing” for the top-level case.
- Hover over the Routing row and click Configure, or Add another rule if one already exists.
- Name the rule something you will recognize later, for example “Catch-all to info@.”
- Under “Envelope recipient,” select “Change envelope recipient” and enter the destination. A Google Group address is usually the better choice than a personal mailbox, because membership can change without touching the rule.
- Leave the “Messages to affect” scope at Inbound unless you have a specific reason to broaden it.
- Save. Changes can take up to 24 hours to apply, so do not panic-test within five minutes and conclude it failed.
Two practical notes before you save. First, the destination mailbox must exist and be verified; a typo in the address produces silent delivery failures, not an error dialog. Second, if you want the original recipient preserved in the headers for sorting later, use “Add more recipients” alongside the envelope change rather than instead of it, since replacing the recipient discards the address the sender actually typed unless you capture it first.
If the Routing row is missing entirely, that is a privilege issue, not a product gap. The Administrator role requires Gmail Settings administrator privilege to see this screen, and a delegated admin without it will find nothing here no matter how carefully they navigate. Confirm your role before you start hunting for a setting that was never shown to you.
Catch-All Limits and Navigation Habits That Save Time
A catch-all rule solves one problem and creates three others. Anyone who has run one for a year will tell you the same thing: the mailbox fills with dictionary attacks, bounced marketing lists, and mail addressed to “info@”, “sales@”, and “admin@” from senders who never had a real relationship with the domain. A catch-all mailbox receives mail for non-existent addresses, and a meaningful share of that traffic is hostile or worthless. Budget for spam filtering that is more aggressive than what your named users get, and expect to review the inbox regularly rather than letting it accumulate.
The second constraint is filtering. Because a catch-all rule applies to inactive and unrecognized accounts, the messages land in one destination with no per-recipient logic. You cannot route “billing@yourdomain.com” to the finance team and “press@yourdomain.com” to comms through the same catch-all action; the routing rule maps unmatched addresses to a single target. If you need per-address behavior, create real accounts, aliases, or Google Group addresses for those addresses and let the catch-all handle only the genuine leftovers. That keeps the catch-all narrow and the routing table readable.
Licensing and recipient validity are the third snag. Google allows a user account or Google Group as destination, and each choice has a cost. Routing to a licensed user account consumes a seat and that user’s storage quota. Routing to a Google Group address avoids the seat but inherits the group’s delivery settings, including whether external senders are permitted and who can post. Groups also need the address to exist and be verified before the rule will accept it. Check both before you save the rule, because changes can take up to 24 hours to apply, and a typo in the destination means a day of silently dropped mail.
On navigation, two habits prevent repeat searches. First, confirm your privilege level before concluding a setting is missing. The Administrator requires Gmail Settings administrator privilege to see and edit routing, and a delegated admin without that role will not find the menu no matter how carefully they click. The Admin console search bar behaves the same way: it returns only what the signed-in account can reach, so a super admin sees results a delegated admin does not. Sign in as a super admin, or ask yours to grant the privilege, before you file a ticket saying the option vanished.
Second, bookmark the path itself. Save a direct link to Apps > Google Workspace > Gmail > Routing (the Gmail Settings “Default routing” area) in your admin bookmarks bar, and note in your runbook that Google Workspace lacks a dedicated catch-all switch under Users or Domains. The catch-all rule uses the Change envelope recipient action inside a routing configuration, which is why it never appears where beginners look first. A short checklist covers the rest:
- Verify the destination address exists and is verified before saving the rule.
- Decide between a licensed user account and a Google Group address, and record why.
- Confirm the signed-in account holds Gmail Settings administrator privilege.
- Allow up to 24 hours after saving, then send a test message to a fake address.
- Review the catch-all mailbox weekly for spam volume and misaddressed email worth redirecting.
None of this makes catch-all routing a bad tool. It makes it a narrow one. Treat the rule as a safety net for misaddressed email, keep the destination lean, and the navigation will stop being the hard part.
Bookmark the path before you need it again: Admin console > Apps > Google Workspace > Gmail > Routing (or Gmail Settings > Default routing). Do it from a super admin session, and note in the bookmark which account you used. The next time a colleague swears the routing menu has vanished, the first question is whether they are signed in as a delegated admin without the Gmail Settings administrator privilege, not whether Google moved the setting. Allow up to 24 hours for a new catch-all rule to take effect, and test it properly: send a message from an outside account to a random address at your domain, then confirm it landed in the catch-all mailbox. A message sent from inside the domain often takes a different path and proves nothing.
One more habit worth forming early. Before you point a catch-all at a personal user account, decide who owns that mailbox and what happens when the person leaves. A Google Group address as the destination survives staff turnover and gives you a shared record of what arrived, while a single user account quietly turns into a backlog nobody reads. Also check the count of addresses you actually need to protect. If the real problem is a handful of former employees or a typo-prone sales alias, a short list of recipient address mappings in the same routing screen is easier to audit than a domain-wide catch-all that accepts every misspelling a spam bot can invent. Set the rule, watch the first week of inbound messages, and adjust from evidence rather than from the assumption that more coverage is always better.
