deploy notes
Comparisons

Email alias vs mailbox: which does your business address need?

Choose an alias, a separate mailbox or shared access based on who reads the mail, who replies and which message history needs to stay private.

Choosing a setup5 min read
In this guide

Use an email alias when one person needs another address in the same inbox. Use a separate mailbox when someone needs their own access or a separate message history. When several people answer one address, look for shared or delegated mailbox access in your current provider.

This guide is for a domain owner who already has an email account and is deciding what hello@studio.example should do. By the end, you should be able to name the right arrangement and the provider capability to check. You do not need to move your domain or buy a new service to make that decision.

An address and an inbox are different things

A mailbox is the place where messages are stored and managed. An alias is an additional address associated with an existing account. Messages to the alias arrive in that account’s inbox; sorting them into a folder does not create separate access permissions.

For example, a sole owner could receive mail for both alex@studio.example and the alias hello@studio.example in Alex’s existing mailbox. If a colleague needs to handle hello@, giving them Alex’s login would also expose Alex’s other mail. An alias does not solve that access problem.

Question Alias on an existing account Separate mailbox Shared or delegated access
Where is mail kept? With the existing mailbox’s messages. In its own mailbox. In a mailbox accessible to authorized people.
Who can read it? Whoever can access the existing mailbox. The account holder and any authorized delegates. The people explicitly granted access.
Does it create a separate user account? No. Usually, for an individual mailbox. Members generally use their own accounts to access it; provider rules vary.
Can you reply from the role address? Check the provider’s send-as support and setup. Normally through that mailbox’s configured address. Check send-as permissions as well as read access.
Does it need another paid seat? Often included, subject to plan limits. Check your included mailbox allowance and license rules. Check both the shared mailbox and member licensing rules.

An alias may be accepted as a sign-in name by some providers, but that still opens the same underlying account. It is not an independent account for a new employee.

Receiving mail does not prove you can reply from the address

Forwarding routes a message to another destination. A domain forwarding service might deliver mail for hello@studio.example into a personal inbox without providing an outgoing mail service for studio.example.

Before choosing that arrangement, ask whether you can send new messages and replies with hello@studio.example in the visible From field. Receiving the message successfully answers only half of the question. Changing a display name does not configure sending from a different address.

Provider behavior is specific. Google Workspace aliases deliver to an existing user’s account; sending from one also needs a custom From address in Gmail. Zoho Mail aliases can send and receive through the existing account, with the alias selected as the From address. These are capabilities to verify in the service you already use, not reasons to switch.

MX records are the domain’s DNS instructions for where incoming mail should be delivered. Adding a role address inside your existing mail provider is a different task from moving those records to a new provider. This choice guide requires neither change.

Choose for the person who will handle the mail

One person, several roles: an alias is often enough. Keep hello@ and billing@ in the same mailbox if the same person can appropriately read and answer both. Check the current alias allowance before paying for another mailbox.

Another person, private correspondence: choose a separate user mailbox with individual access. This lets you give the person their own account rather than access to your entire inbox.

Several people, one customer address: check shared or delegated access. Delegation means granting someone permission to use a mailbox from their own account. Google’s delegation documentation is one example of that model. Verify the permissions and whether everyone can see sent replies, so two people do not independently answer the same request. Do not treat forwarding copies to several inboxes as equivalent to a shared conversation history.

Finish with a clear address plan

Write one line for each address: who reads it, where its messages live, who may reply and which From address customers should see. If all four answers point to your existing mailbox, check its alias feature. If access or history must be separate, use a separate mailbox or shared inbox for that role address. Grant access to that mailbox only. Delegating your personal mailbox would expose its other mail; it would not isolate messages sent to an alias.

If another mailbox is necessary, the business email cost guide helps you count the required seats and compare billing terms.

After you eventually configure the selected arrangement, verify both an incoming message and a reply before putting the address on your website. Inspect the reply in the recipient’s inbox to confirm its actual From address. That later check establishes the behavior; the choice of a product name alone does not.

← Back to comparisons guides