Gmail Aliases for Teams: 30 Per User, One Inbox Owner

Use a Google Group or a delegated shared mailbox for any address more than one person sends from or replies to. Use a Gmail alias only when a single person owns the address, even temporarily. The immediate action: in the Google Workspace admin console, create a Group with collaborative inbox settings for shared mail, and reserve Gmail’s Send mail as feature for individual users who need a second identity.

TL;DR:

• Workspace permits up to 30 aliases per user at no extra cost, but each address belongs to one person and routes into that person’s inbox.
• Delegation supports up to 1,000 delegates on one account, although Google recommends keeping concurrent delegates closer to 40 for reliable performance.
• A collaborative Google Group sends incoming mail to multiple members, while explicit thread ownership and consistent sender names help prevent duplicate or conflicting replies.
• Deleting an alias leaves previously delivered messages in the mailbox, but new mail sent to that address bounces, so notify senders before removal.
• Gmail may suppress messages you send to your own alias or Group; check Sent or All Mail, or add the address under Send mail as.

Table of Contents

• What a Gmail alias actually is and where it fits
• How admins add, list, and remove email aliases
• Setting up Send mail as and the Treat as an alias option
• Alias vs delegation vs Google Groups: picking the right setup
• Fixing the most common alias and shared inbox problems
• Best practices for keeping team mail organized at scale
• What running high-volume Gmail sending actually teaches you
• FAQ
• Sources

What a Gmail alias actually is and where it fits

A Gmail alias is an alternate email address that routes directly into one person’s existing inbox. It is not a separate Google Account: there is no separate login, no separate storage, and no separate set of permissions. Mail sent to the alias lands in the same place as mail sent to the primary address, which is exactly why aliases break down the moment more than one person needs to see or answer that mail.

Aliases work well in a narrow set of situations:

• A solo consultant or freelancer who wants a professional-looking address without a second account
• A short-term project address that needs to disappear once the work wraps up
• A retired employee’s address that should still catch stray mail and forward it to whoever took over

Each alias can only belong to one user at a time, and Workspace lets you add up to 30 aliases per user at no extra cost. That quota is generous for personal use, but it does nothing to solve team mail: thirty aliases on one account still means one inbox, one owner, one person responsible for every reply.

How admins add, list, and remove email aliases

Adding and removing aliases correctly avoids the most common cleanup headache: an address that quietly stops working because two systems both think they own it.

Before you add an alias:

1. Confirm the address is not already a Google Account, a Group address, or an alias on another user, since Workspace will reject a duplicate.
2. Sign in to the Admin console and go to Directory, then Users, and open the target user’s profile.
3. Under User information, select Alternate email addresses (sometimes shown as Alias) and enter the new address.
4. Save, then reopen the user record to confirm the alias appears under their account, since propagation can take a few minutes.
5. For bulk additions across many users, use the Admin SDK Directory API or a bulk update spreadsheet rather than adding aliases one at a time.

To see every alias on an account, open the same Alternate email addresses panel on the user record, or query the Directory API if you manage aliases programmatically across a larger org.

Removing an alias is just as direct: delete the entry from the same panel. Mail already delivered under that address stays in the recipient’s mailbox history, but any new mail sent to the removed alias will bounce, so warn anyone still using it before you pull it.

Pro Tip: Keep a simple spreadsheet mapping every alias to its owner and purpose. Aliases are invisible in most reporting views, and an orphaned alias is a common source of missed client mail.

Setting up Send mail as and the Treat as an alias option

Once an alias exists on the Workspace side, the user still needs to tell Gmail to send from it. That happens entirely inside Gmail, not the admin console.

• Open Gmail Settings, go to Accounts, and under Send mail as, select Add another email address.
• Enter the address and confirm ownership, which usually happens automatically for addresses already set up as Workspace aliases.
• Choose whether to check Treat as an alias.

That checkbox matters more than it looks. According to Gmail’s own documentation, checking “Treat as an alias” changes how Gmail handles delivery and replies: messages sent to that address behave as if sent to the primary account, and the reply-to behavior follows the primary address rather than the alias. Leaving it unchecked keeps the alias behaving more like a distinct sending identity, affecting reply threading and reply-all behaviors.

Non-Gmail addresses work differently. Adding a true third-party address through SMTP requires server credentials rather than Workspace’s built-in alias verification, and that path is where most setup errors show up.

A quota worth knowing: up to 30 aliases per user at no additional cost, which covers nearly every solo use case before you’d ever need a second account.

The practical effect for teams: outbound tracking tools and sent-mail visibility depend on which address actually sent the message, so mixing alias settings across team members makes audit trails inconsistent fast.

Alias vs delegation vs Google Groups: picking the right setup

The decision comes down to one question: does this address have one owner, or several?

• Single owner, one person responsible for every reply: use an alias.
• Multiple people need to read and respond, and replies should look like they come from the team: use a Google Group with collaborative inbox turned on, or delegate access to a shared mailbox.

The trade-offs are concrete. Aliases guarantee ownership clarity but can’t scale past one person. Delegation gives delegates the ability to read, send, and delete messages on someone else’s behalf, with a single account supporting up to 1,000 delegates, though Google’s own performance guidance recommends keeping concurrent delegates closer to 40 for reliability. Groups add an address that can carry its own aliases and route mail to multiple members at once, which solves the duplicate-reply problem that plagues shared aliases.

Admin guidance is explicit that aliases can’t be delegated: once a team outgrows one owner, the alias has to be replaced, not extended.

Pro Tip: If you’re debating whether to add a fourth or fifth person to an alias workflow, that’s the signal to convert to a Group instead. Aliases don’t scale gracefully; they just get messier.

Fixing the most common alias and shared inbox problems

Most alias support tickets trace back to a handful of repeat issues.

1. Mail sent to your own alias or Group doesn’t show in your Inbox. This is expected behavior, not a bug: Gmail suppresses delivery of self-addressed mail to avoid clutter. The documented fix is adding the alias as a Send mail as address, or checking Sent and All Mail.
2. Verification fails when adding a send-as address. Double-check the address isn’t already claimed elsewhere, and resend the confirmation link if it expired.
3. SMTP or TLS errors on third-party addresses. These point to incorrect server settings, not a Workspace alias problem, since true aliases skip SMTP entirely.
4. Delegates or Group members report missing mail. Check membership status and delegate permissions first; a removed or pending member stops receiving mail silently.
5. Bulk sends stall or bounce. External recipient caps and daily sending limits can throttle high-volume outbound mail, which shows up as delayed delivery rather than a clear error.

Best practices for keeping team mail organized at scale

Once an address serves a team, structure matters more than setup. A few habits keep queues manageable:

• Use filters and labels to route incoming mail by topic or sender, so no one’s digging through a shared inbox manually.
• Assign explicit ownership for each thread, even informally, so two people don’t send conflicting replies to the same lead.
• Standardize the From display name and signature across everyone sending from a shared address, so recipients see one consistent voice.
• Review delegate activity periodically, and convert the setup to a dedicated shared mailbox once the volume outgrows informal delegation.

Pro Tip: Treat the move from alias to Group to shared mailbox as a growth ladder, not a one-time decision. Revisit it every time headcount on that address changes.

What running high-volume Gmail sending actually teaches you

Running offers through individual Gmail accounts at volume surfaces a pattern most alias guides skip: the mechanics of aliases and delegation are simple, but the operational discipline around them is not. We’ve watched teams try to stretch a personal alias across three or four people because setting up a proper Group felt like overkill, and it never holds. Replies get duplicated, nobody’s sure who answered what, and tracking opens and follow-ups becomes guesswork instead of a system.

The real threshold isn’t a specific headcount. It’s the moment a second person starts replying from the same address regularly. That’s when informal setups start costing more time than they save, and when structured sending workflows start paying for themselves instead of adding overhead.

— Shane

FAQ

What is the Gmail alias trick?

The common “Gmail alias trick” refers to adding symbols or dots to your Gmail address, since Gmail ignores dots and treats anything after a plus sign as part of the same inbox. This is different from a Workspace alternate email address, which is a separate address an admin configures to route to a primary inbox.

Can a Gmail account be used for Microsoft Teams?

Gmail accounts are not tied to Microsoft Teams, which runs on Microsoft identities rather than Google accounts. Some organizations use a Gmail address as a contact point or guest login for Teams, but the alias and delegation features described here are specific to Google Workspace.

Can Gmail addresses have aliases?

Yes. A Google Workspace admin can add up to 30 alternate email addresses to a single user at no extra cost, and each one routes directly into that user’s existing inbox. An alias is not a separate account, and only one user can hold a given alias at a time.

What should I check before relying on email aliases for team use?

Confirm whether more than one person needs to send or reply from the address, since aliases only support a single owner and can’t be delegated. If multiple people need access, a Google Group with collaborative inbox or a delegated shared mailbox avoids the duplicate-reply and ownership confusion that aliases create under shared use.

Sources

• Add or delete an alternate email address (email alias) | User management | Google Workspace Help
• Send emails from a different address or alias - Gmail Help
• Give a group an additional alias address | Google Workspace Help