Five Checks Before Adding a Google Workspace Alias

AST Logistics Services > Blog > Updates > Five Checks Before Adding a Google Workspace Alias

Adding an alias in Google Workspace looks like a two-click job in the Admin console, which is exactly why so many tenants end up with mail landing in the wrong mailbox. The failure modes are quiet: no error dialog, no bounce, just a message that disappears into a group or a colleague’s inbox. Before you type a new alias address into the console, run these checks. They take five minutes and prevent the kind of ticket that takes a week to untangle.

Confirm the alias is unique across the whole tenant, not just the user

The Admin console will reject an alias that already belongs to another user, but it is far less reliable about collisions with group addresses, and that gap is where most delivery problems start. Gmail resolves recipients in a fixed order, and a group address that matches an alias can win, which means mail intended for one person gets fanned out to a distribution list or, worse, silently dropped if the group restricts external posting. Before you create anything, search the entire directory for the exact string you plan to use. That means checking users, groups, and any resource calendars that carry an email address.

Tenant-wide uniqueness is the rule Google documents on its help pages, but the console enforces it unevenly across object types. A user alias that duplicates a group address is the classic collision: john.smith@yourdomain.com exists as a group for the sales team, and someone later tries to add it as an alias for a new hire named John Smith. The console may accept the alias because the group is a different object class, and then inbound mail routes to the group. The new hire gets nothing, the sales team gets confused, and the sender sees no error.

Do the search in the directory first, not the alias dialog. Look at suspended users too, since their aliases still reserve the address and will block the new one without a clear explanation. If you find a collision, the fix is to rename or retire the older object, not to force the alias through. Keep a short note in your ticket about what you checked so the next admin does not repeat the work.

Verify the domain and the alias limit before you touch the console

An alias can only live on a domain your tenant has verified and that is set as a secondary domain or domain alias. If you are adding the alias on a domain that was recently purchased or migrated, confirm the verification record has propagated and that the domain shows as verified in the Domains section. An unverified domain will not accept aliases at all, and a domain alias behaves differently from a secondary domain: aliases created on a domain alias are tied to the primary domain’s user, so plan the naming accordingly.

Check the 30-alias ceiling per user

Google Workspace allows 30 aliases per user, and that count includes every alias across every domain in the tenant. A user who has accumulated aliases over years of department changes may already be near the ceiling, and the console error when you hit it is not always obvious about which limit you crossed. Pull the user’s current alias list before you add anything. If the user is at 30, you have two options: remove stale aliases that no longer receive mail, or split the addresses across a second account. Removing aliases is safe for delivery as long as nothing is still addressed to them, so check the mail logs for recent traffic before you delete.

This is also where people confuse Workspace aliases with the consumer Gmail feature set. On a personal account, Gmail plus aliases let a single user generate unlimited address variants by appending +tag to the base address, and all of those deliver mail to the same inbox without touching any limit. Workspace users have that same plus-alias capability on top of their 30 named aliases, so a user who needs a hundred signup addresses does not need a hundred aliases. As the AllMail guide to Gmail aliases explains, plus aliases are best for anything disposable, while named aliases should be saved for addresses that need to appear in a From field.

Decide whether Send mail as is actually required

An alias receives mail but does not automatically let the user send from it. That requires configuring Send mail as, which in Workspace is usually handled by the admin or by the user through Gmail settings under Accounts and Import. The configuration needs an SMTP server, typically smtp.gmail.com on port 465 or 587, plus an app password or OAuth grant depending on how the tenant enforces security. A verification email goes to the alias address to prove ownership, and in Workspace that message lands in the user’s own inbox, so the user has to click through it.

Send mail as supports up to 99 addresses per user in a Workspace account, which is generous but not unlimited. Plan for the day a heavy user hits it. One relevant change on the horizon: Gmail will discontinue Send as for third-party addresses starting January 2027, so any workflow that relies on sending through an external SMTP provider from Gmail needs a migration plan. Native Workspace aliases on your own verified domains are not affected, which is one more argument for consolidating on aliases rather than external send-as entries.

Trace the delivery path and document what the alias is for

Before you save, answer one question in writing: where should mail to this alias land? For a user alias, the answer is the user’s inbox, and that is usually fine. For an alias that resembles a role or team name, the answer is often a group, and creating it as a user alias is the wrong move. If the address is billing@ or support@, it belongs on a group or a collaborative inbox so more than one person can see it and so it survives someone leaving. A user alias tied to a person becomes an orphan the day that person’s account is suspended.

Routing also depends on how the tenant handles catch-all and forwarding rules. If a catch-all is configured, any address on the domain that does not match an object will still deliver somewhere, which can mask a misconfigured alias for weeks. Check the routing settings and the default routing rules before you assume a test message proved anything. Send a test from an external account, not from inside the tenant, because internal mail can take a different path through the same domain and hide a problem.

Existing Gmail filters can be created on plus alias addresses, and users often build filters around a specific alias before the alias exists. If you are renaming or replacing an alias, those filters break silently. Ask the user whether any filters reference the address, and if so, have them update the filter criteria in the same change window. The same applies to any third-party service that has the old address on file as a recovery contact.

Document the alias with its purpose, owner, and creation date in whatever inventory you keep. A one-line entry in a shared sheet beats a forensic exercise six months later when someone asks why an address exists and who receives it. If your organization publishes internal guides, AllMail publishes Gmail alias guides that cover the consumer side of plus aliases and dot aliases, which is useful context for users who assume Workspace and personal Gmail behave identically. They do not, and the differences are exactly the ones that cause support tickets.

Run the five checks in order: search the tenant for the exact string, confirm the domain is verified and know whether it is a secondary domain or a domain alias, count the user’s existing aliases against the 30-alias ceiling, decide whether Send mail as is needed and whether the user is near the 99-address cap, and trace where the mail should actually land. Keep a record of the result. If any check fails, fix the underlying object rather than working around it, because a forced alias will eventually route mail to the wrong place and the sender will never tell you. Admins who want a second address with a truly separate inbox should create a second Google account or a dedicated Workspace user instead of stacking aliases on one account, since a second Google account provides a separate inbox and separate security surface. The alias is a convenience, not a substitute for proper account design.