Skip to content

Knowledgebase

Adding a Google Workspace email alias and testing replies

email

A Google Workspace email alias sends mail addressed to another name into an existing user's mailbox. It suits a person handling several roles, such as [email protected] and [email protected]. It is not a separate Google account and cannot be used as an independent sign-in.

01 Add the alias

  1. In the Admin console, open Directory > Users and select the intended mailbox owner.
  2. Choose Add Alternate Emails. Enter the local part of the address and select an eligible domain.
  3. Check the spelling and confirm that the address is not already a user, group or another alias.
  4. Save the change and allow time for it to apply.
  5. Send a message from an unrelated external account to the alias and confirm it reaches the owner's existing inbox.

02 Configure replies deliberately

Receiving mail through an alias does not establish the desired From address for every reply. In the owner's Gmail settings, review the supported Send mail as configuration and add or select the alias as needed. Send a test reply and inspect the address shown to the recipient.

03 Example: receive accounts mail in one existing Gmail inbox

Ada already uses [email protected] and is the only person handling supplier invoices. Add [email protected] as an alias of her account rather than creating another independent user.

  1. Open Directory > Users in the Admin console and select Ada.
  2. Choose Add Alternate Emails, enter accounts and select the eligible domain.
  3. Save, allow the change to apply and send a controlled external message to the alias.
  4. In Ada's Gmail settings, review Send mail as if replies should use the accounts address.
  5. Reply to the test and inspect its received From address.

Expected result: alias mail arrives in Ada's existing inbox, and replies use the identity you deliberately configured. The alias does not create a separate Google account.

When should I use a group instead?

If several people need the messages, a group or an appropriately delegated mailbox is usually easier to manage than sharing the owner's password. An alias belongs to one primary account and does not provide an independent conversation assignment workflow.

04 Changing an alias later

Inventory forms, customer records and published contact pages using the old address before removing it. Removing the alias affects future delivery to that address but does not sort or transfer messages already in the mailbox.

If a test fails, verify the alias in the Admin console, check the domain's mail activation and read the sender's rejection. A misspelled or unavailable address needs a different remedy from a message filtered into Spam. Keep a record of who owns role addresses so they can be reviewed during staff changes.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support