Google Workspace Email Routing Rules: How They Actually Work

Google Workspace email routing rules are admin-level settings that decide where a message goes before it ever reaches a user's inbox. Unlike Gmail filters — which a user sets and which act on already-delivered mail — routing rules are configured in the Admin Console and operate at the domain delivery layer. A routing rule can redirect mail to an external server, copy it to two inboxes at once, or reject it outright before any user filter ever sees it.

The configuration itself is not complicated. The part that breaks real deployments is precedence. Google Workspace evaluates all active rules against every incoming message independently, compiles a consequence list, and then applies a hierarchy to resolve conflicts. If you add a rule without knowing where it sits in that hierarchy, it can silently lose to an older or more specific rule — and the message goes somewhere unintended, with no visible error.

The short answer#

Google Workspace organises its routing configuration into two primary settings in the Admin Console: Default routing and Routing. Default routing establishes organisation-wide delivery behaviour; the Routing setting creates per-recipient or per-OU rules that override it. Compliance settings — Content compliance and Attachment compliance — live in a separate section but interact with routing through the same consequence hierarchy.

The evaluation order, from highest to lowest priority: reject actions fire first regardless of where they appear; compliance rules sit above default routing; per-OU Routing rules override inherited Default routing for that OU's users; Default routing applies last, with the admin manually controlling the order inside that section. When two rules in the same layer conflict on a routing action, the older rule wins unless you reorder explicitly.

All three main routing types are in Admin Console > Apps > Google Workspace > Gmail. Default routing and the Routing setting are in the Routing section; Content and Attachment compliance are in the Compliance section just below it.

Before you start#

Routing rules require admin access. Standard user accounts cannot configure them, and delegated accounts with limited roles see the Routing section as read-only.

• Role required: Super Admin, or a custom admin role with the Services > Gmail > Settings privilege.
• Navigation: Admin Console > Apps > Google Workspace > Gmail. Scroll to the Routing section. Default routing and Routing appear as separate expandable subsections.
• Propagation time: changes take up to 24 hours to become active across all of Google's infrastructure. Most apply within the hour, but wait the full window before concluding a rule is broken.
• Scope: routing rules apply only to active users with Gmail enabled. Suspended accounts and users with Gmail turned off are not covered — their mail follows the domain MX record, not these rules.

Set up default routing#

Use Default routing for domain-wide rules: redirecting all inbound mail to an external server, running dual delivery during a migration, or routing messages that match a recipient pattern. It is the broadest-scope routing tool available and the one most deployments start with.

1. 1

   Open Default routing

   Admin Console > Apps > Google Workspace > Gmail. Scroll to the Routing section and expand it. Click Configure under Default routing. If you have existing rules, click Add another rule instead.

2. 2

   Set the recipient match

   Under Specify envelope recipients, choose how to match incoming messages. All recipients applies the rule to every inbound message for the domain. Single email address targets one address. Regexp matches a pattern — Google uses RE2 syntax here. Groups applies to messages sent to a specific Google Group address.

3. 3

   Choose the action

   Under Do the following, select Modify message to change delivery behaviour, or Reject message to block delivery with a custom error. For Modify message, enable Route and select an SMTP host to send the message to an external server, or leave the default Gmail delivery and modify headers, footers, or envelope recipients.

4. 4

   Enable dual delivery (optional)

   Within the Modify message action, check Also deliver to and enter a second destination: an email address, a named SMTP route, or a Google Group. Both deliveries happen in parallel — a failure at one destination does not block the other.

5. 5

   Set the rule priority

   New rules default to the lowest priority within Default routing. To reorder, click Reorder next to any rule, enter a number (1 is highest), and save. Rules with a Reject action always rank above all other Default routing rules regardless of the number you assign.

6. 6

   Save and verify

   Click Save. Send a test message matching the rule criteria, then check Admin Console > Reporting > Email log search to confirm which rules matched and what action each applied. Do not test immediately after saving — allow a few minutes for the change to take effect.

Set up per-recipient routing#

The Routing setting — distinct from Default routing — creates rules scoped to a specific OU, set of addresses, or address pattern. Because it applies at the OU level rather than domain-wide, it overrides any conflicting Default routing rule inherited from a parent. Use it when a subset of your organisation needs different delivery behaviour: a department whose mail must route through a compliance gateway, or a role address that needs to land somewhere other than Gmail.

1. 1

   Navigate to Routing

   Admin Console > Apps > Google Workspace > Gmail. Scroll to the Routing section and click Configure under Routing — this is a separate button from the Default routing Configure button.

2. 2

   Scope the rule

   Under Envelope recipients, specify which users this rule covers: a specific OU, individual addresses, a regex pattern, or a Google Group address. The rule applies only to messages addressed to users within this scope.

3. 3

   Configure the action

   Choose Modify message, Reject message, or Quarantine. For Modify message, configure the route: an external SMTP host, a change to the envelope recipient, or added routing headers for downstream systems.

4. 4

   Save

   Click Save. This Routing rule overrides any conflicting Default routing rule for users in the specified OU. If a conflicting Routing rule exists at a child OU, the child-OU rule wins for users in that sub-group.

Configure dual delivery#

Dual delivery copies the same incoming message to two destinations simultaneously. Both inboxes receive it; neither blocks the other. Common uses: running Google Workspace alongside a legacy mail server during a phased migration, or delivering every inbound message to Gmail and a compliance archiver in parallel.

Dual delivery is an action within a routing rule, not a separate rule type. You enable it inside any Default routing or per-recipient Routing rule.

1. 1

   Create or open a routing rule

   Follow the Default routing or per-recipient Routing steps above. Open the rule that should apply to the messages you want to duplicate.

2. 2

   Enable Also deliver to

   Within the Modify message action, check Also deliver to. Enter the second destination: an email address, a named SMTP route configured under Gmail > Hosts, or a Google Group. You can add more than one secondary destination.

3. 3

   Save and test both legs

   Save the rule. Send a test message and confirm delivery at both destinations. Use Reporting > Email log search to verify both delivery legs if either is uncertain — Gmail logs each delivery attempt separately.

How routing rule types compare#

Google Workspace evaluates all active rules against every incoming message independently. Once it has a complete list of matching consequences, it resolves conflicts using specificity and age: rules applied directly at an OU beat rules inherited from a parent; within the same specificity level, older rules beat newer ones. The table below shows where each rule type sits in that hierarchy.

The practical implication: a Default routing rule you create today loses to a Content compliance rule set last year, even if the compliance rule is less specific to the message you are targeting. When two rules in the same layer conflict, the only solutions are an explicit Reorder or moving the logic to a higher-priority layer.

When a routing rule is not working#

Routing rules fail quietly. The message does not bounce — it arrives somewhere unexpected, or does not arrive at all. Work through the causes below before assuming the rule itself is wrong.

• A higher-priority rule already matched the message. A Content compliance rule, an Attachment compliance rule, or an older Default routing rule that matches the same message will have its routing consequence applied instead of yours. Open the Routing settings page and look for older rules in the same or a higher layer.
• The target account has Gmail turned off or is suspended. Routing rules do not apply to these accounts. Their mail follows the domain MX record, not the rules you configured.
• Propagation is not complete. Save and wait the full 24-hour window before concluding a rule is broken. Testing immediately after saving is not reliable.
• Regex mismatch in the recipient pattern. If you matched recipients using a regular expression, test the pattern using RE2 syntax specifically. A pattern that looks correct in a standard tester may behave differently in Google's RE2 implementation.
• Silent failure on the second leg of dual delivery. If the second destination in a dual delivery rule is unreachable or rejects the connection, Gmail logs the failure but still delivers to the primary destination. The rule appears to work, but the copy never arrives. Use Email log search to check both delivery legs explicitly.

A faster way to manage routing for your inbox#

Routing rules are the right tool for domain-level delivery decisions: redirecting a department's mail through an external gateway, running dual delivery during a migration, catching unaddressed messages with a catch-all rule. They operate before delivery and have no context about a sender's relationship to the recipient, the urgency of a thread, or what needs a response today.

AI Emaily's Rules Brain and Context engine work at the inbox layer instead. You define what matters — clients, projects, priority senders — and the agent handles triage, labelling, and follow-up queuing across every message that arrives, without needing an admin role or a propagation window. It works across Gmail, Outlook, and any IMAP account, so Workspace routing rules and AI Emaily operate at different layers and do not conflict: one controls where messages land; the other manages what happens to them once they do.

We build AI Emaily.