Shared Mailboxes and Email Aliases: Organizing Your Team's Communication
It starts innocently. Someone creates an info@ address for the business, shares the password in a WhatsApp group and moves on. Six months later, three people are logged in at once, two of them replied to the same customer, a supplier's invoice has been sitting unread for a week, and nobody remembers who has access to what. When a team member leaves, the password is still in their phone.
Shared mailboxes and email aliases solve this. They let a team send and receive from addresses like info@, sales@ and support@ without sharing passwords, losing messages or making customers wait. But the terms get mixed up, and the right tool depends on your team size and email platform.
This guide explains the difference between shared mailboxes, aliases, forwarders and groups, shows how each works on cPanel, Microsoft 365 and Google Workspace, and walks you through setting up team email that stays organized, secure and easy to manage.
Key takeaways
An alias is an extra address that delivers into an existing mailbox. A shared mailbox is a mailbox several people can open and send from using their own logins. A group or distribution list copies incoming mail to several people.
Never share one mailbox password among a team. Use aliases, forwarders, groups or shared mailboxes with individual access instead.
Small teams can often manage with aliases and forwarders. As volume grows, move to a true shared inbox so everyone sees the same conversation history.
Give each role-based address one clear owner, plus a backup.
Review who has access whenever someone joins, changes role or leaves.
On SteboHost, you can run professional Business Email on your domain, or choose Google Workspace or Microsoft 365 when you need richer collaboration features.
The Problem With Unmanaged Team Email
Teams that share one login or forward everything to one person's inbox run into the same issues:
Missed or delayed messages because everyone assumes someone else is handling it
Duplicate or conflicting replies when two people answer the same customer
No accountability, because nobody can tell who saw or sent what
Security risk, since a shared password is hard to change, easy to leak and impossible to audit by person
Lost history when the person who owned the inbox leaves
A bad customer experience, with replies coming from different personal addresses instead of one consistent business address
Key Terms Explained
Term | What it is | Typical use |
|---|---|---|
Mailbox | A real account with its own storage, login and inbox | One person's work email |
Alias | An extra address that delivers into an existing mailbox | sales@ delivering to one person's inbox |
Forwarder | A rule that sends a copy of mail for one address to another address | info@ forwarded to two or three people |
Group or distribution list | An address that fans messages out to its members | team@ reaching everyone in a department |
Shared mailbox | A mailbox several people open from their own accounts, with a shared inbox and sent items | support@ handled by a small team |
Delegation | Giving another person access to someone else's mailbox | An assistant managing a director's email |
Catch-all | A rule that delivers mail for any address that does not exist on your domain | Capturing mistyped addresses, with a spam trade-off |
Different platforms use these words slightly differently. In cPanel there is no separate alias feature, for example: an alias there is simply a forwarder that points at a mailbox.
Which One Do You Need?
Situation | Best fit |
|---|---|
One person should receive mail for several addresses (info@, orders@, billing@) | Aliases or forwarders into that person's mailbox |
Two or three people need to see every message sent to one address | Forwarders to each person, or a group |
A team needs to read, reply and see who answered, from one address | Shared mailbox or shared inbox group |
Everyone in a department needs an announcement | Distribution list or group |
An assistant needs access to a manager's inbox | Delegation |
An employee left and customers still write to them | Alias or forwarder to their successor |
A simple rule of thumb: if people only need to receive mail, aliases, forwarders or groups are enough. If people need to collaborate on replies, you need a shared mailbox or shared inbox.
How It Works on Common Email Platforms
cPanel-based email
If your mailboxes are managed in cPanel, the building blocks are straightforward:
Email Accounts create real mailboxes with their own logins.
Forwarders send a copy of mail for one address to another address. cPanel has no separate "alias" feature, so you create a forwarder that points an extra address at a mailbox. To deliver to several people, you add one forwarder per recipient.
Default Address (the catch-all) decides what happens to mail sent to addresses that do not exist. Forwarding everything to one inbox attracts a lot of spam, so discarding or rejecting unknown addresses is generally the safer setting.
Domain forwarders redirect mail for an entire domain to another domain.
This setup is simple, reliable and cheap. Its limit is that forwarders create separate copies: each recipient has their own message, so nobody can see who replied, and each person's reply comes from their own mailbox. For a busy support or sales address, that is where a real shared mailbox becomes worth it. Standard cPanel email does not typically include a shared mailbox with per-person permissions, so teams that need one usually move to a collaboration suite.
Microsoft 365
Microsoft 365 has true shared mailboxes:
Several people open the shared mailbox from their own accounts, so there are no shared passwords. The shared mailbox itself does not allow direct sign-in.
Access is granted with three permissions: Full Access (read and manage messages), Send As (messages appear to come from the shared address) and Send on Behalf (messages show the sender acting for the shared address). Full Access alone does not allow sending.
Shared mailboxes need no license of their own up to 50 GB, but every person who uses one needs their own Exchange Online license. A larger mailbox, an in-place archive or a litigation hold requires an Exchange Online Plan 2 license.
Outlook can add the mailbox automatically (automapping), which works for individually assigned users, not for security groups.
If you also need to collaborate with files, chat and calendars, a Microsoft 365 group may suit better than a shared mailbox.
SteboHost offers Microsoft 365 if this is the right fit for your team.
Google Workspace
Google Workspace offers a few options:
Aliases: an admin can add up to 30 alternate addresses per user at no extra cost. Mail sent to an alias lands in that user's inbox. An alias belongs to one person: only one user receives the mail, although others can send from it if they set up a custom From address.
Delegation: one user gives others access to their mailbox. Google allows up to 1,000 delegates per account, and recommends keeping it to around 40 for the best performance. You cannot assign delegates to an alias, because an alias is not a separate account.
Google Groups and collaborative inboxes: for a shared address used by several people, Google recommends groups. A collaborative inbox lets team members read and respond to messages sent to the group, with replies coming from the shared address.
SteboHost offers Google Workspace if your team prefers Gmail's interface and Google's collaboration tools.
Role-Based Addresses Every Business Should Consider
Role addresses stay the same even when people change. Customers, suppliers and automated systems all expect some of them.
info@ for general enquiries
sales@ for new business
support@ or help@ for customers
billing@ or accounts@ for invoices and payments
orders@ for an online store
hr@ or careers@ for applications
admin@ for system notifications and account recovery
webmaster@ for website-related mail
postmaster@ and abuse@, which are standard role names that mail systems and other administrators expect to be able to reach
Avoid no-reply@ for customer communication. It tells people you do not want to hear from them, and it blocks the simplest way for them to reply.
Step-by-Step: Set Up Team Email That Works
Step 1: List what you have
Write down every address your business uses, who reads it, who is supposed to answer it, how mail reaches them and who knows the password. You will probably find forgotten addresses, orphaned forwarders and shared passwords.
Step 2: Assign roles and owners
Give each role address one owner responsible for making sure messages get answered, and one backup for leave and busy periods. Decide target response times, for example the same business day for sales enquiries.
Step 3: Choose the right tool for each address
Use the table earlier in this guide. As a starting point for a small team:
Low-volume addresses such as admin@ or billing@: alias or forwarder to the responsible person
Medium-volume addresses such as info@: forwarders to two or three people, with a clear rule about who replies
High-volume addresses such as support@ or sales@: a shared mailbox or shared inbox group, so everyone sees the same thread and who answered
Step 4: Create the addresses
In cPanel, open Email Accounts for real mailboxes, and Forwarders to point role addresses at them. In Microsoft 365, use the admin center to create a shared mailbox and assign permissions to named people. In Google Workspace, add aliases in the Admin console, or create a group with a collaborative inbox. Always give access to individuals, not to a shared login.
Step 5: Set up sending properly
Customers should see a consistent address when they get a reply. Depending on your platform, set up Send As or a custom From address so that replies come from sales@ rather than from a personal mailbox. Make sure the domain's SPF, DKIM and DMARC records cover every system that sends mail on your behalf, so your messages are trusted and reach the inbox. SteboHost Business Email configures SPF, DKIM and DMARC automatically, and you can review your records in managed DNS.
Step 6: Agree how the team works the inbox
Technology only helps if people use it the same way. Agree simple rules:
Claim before you reply. Use a flag, category, folder or a quick internal note so two people do not answer the same message.
Reply from the shared address, not from personal mailboxes.
Keep one signature style for each address.
Use templates for common questions, and an auto-responder that sets expectations on response time.
Plan cover for holidays, with a backup who can see the inbox.
Know when to upgrade. If you are tracking assignments and response times by hand, a dedicated helpdesk tool may serve you better than email alone.
Step 7: Secure everything
Turn on multi-factor authentication for all accounts that support it.
Use strong, unique passwords for each person, and never share them.
Give people only the access they need, and review it regularly.
Remove access immediately when someone leaves or changes role.
Be careful with what you put in email. See website security for how to protect the accounts and sites around your email.
Step 8: Test and train
Send test messages to every address from outside your organisation, including a Gmail or Outlook address. Confirm each one arrives, that replies come from the right address, and that nothing lands in spam. Then show the team how the setup works.
Naming and Organisation Tips
Pick one naming convention (first.last@ or first@) and apply it to everyone.
Keep role addresses short and obvious.
Document every address, owner, backup and purpose in one shared place.
Retire addresses you no longer use instead of leaving them open.
Review the list every quarter.
When Someone Leaves: An Offboarding Checklist
Remove their access to shared mailboxes, groups and delegated inboxes.
Reset their password and sign out of devices.
Redirect their address to a successor, or keep it as an alias, so customers are not left without a reply.
Hand over or archive important mail according to your retention policy.
Remove them from distribution lists and role-address forwarders.
Update your address documentation.
Because email often contains customers' personal data, handle it with care. If your business operates in Kenya, our guide to the Data Protection Act explains what to consider when it comes to storing, sharing and deleting personal information.
Common Mistakes to Avoid
Sharing one password across the team
Turning on a catch-all that forwards everything to one inbox and drowns it in spam
Forwarding to external addresses without testing. Forwarded mail can occasionally fail authentication checks at the destination, so test it, or use a group or shared mailbox instead
Creating forwarding loops, where address A forwards to B and B forwards back to A
Using forwarders for something that needs collaboration, so nobody can see who has replied
Forgetting to review access after staff changes
Letting mailboxes fill up and start bouncing messages
No documented owner for each address
Why Run Your Team Email on SteboHost
Whether you are a team of three or thirty, SteboHost helps you keep email professional and under control:
Business Email on your own domain, such as you@yourcompany.co.ke, with webmail, IMAP and POP3 access and spam and virus filtering included.
SPF, DKIM and DMARC configured automatically, so your messages are set up to reach the inbox.
Mailboxes included with hosting: The number of mailboxes depends on your plan, as listed on the plan limits page, so a website and team email can live under one roof.
Room to grow: move to Google Workspace or Microsoft 365 when you need shared mailboxes, shared calendars and collaboration tools.
Free migration on annual plans, covering your site, databases, email and DNS, so changing providers does not mean losing messages.
Local support on +254 703 610 464 and billing in KES by M-Pesa, card or bank transfer, with renewal prices shown before you pay.
Current plan and renewal prices are shown before you buy. Explore SteboHost Business Email, compare plans and pricing, or browse the knowledge base for email setup guides.
Conclusion
Good team email is not about more tools. It is about the right tool for each address: aliases and forwarders for simple routing, groups for distribution, and shared mailboxes when people need to work a conversation together. Give every address an owner, never share passwords, review access when people come and go, and test your setup from the outside. Your customers will see a team that answers quickly and speaks with one voice.
Ready to organise your team's communication? Explore SteboHost web hosting with included business email, or contact the team or call +254 703 610 464 and SteboHost will help you choose the right setup.
Frequently Asked Questions
What is the difference between an email alias and a shared mailbox?
An alias is an extra address that delivers into one existing mailbox, so one person sees the mail. A shared mailbox is a mailbox that several people open from their own accounts, with a common inbox and sent folder. Use an alias to give one person several addresses. Use a shared mailbox when a team needs to answer the same address together.
Can several people use the same email address?
Yes. Common ways are forwarding the address to each person, a group or distribution list, a shared mailbox or shared inbox, or delegation. Each person should use their own login instead of sharing one password, so you can control and audit who has access.
Do shared mailboxes cost extra?
It depends on the platform. In Microsoft 365, a shared mailbox needs no license of its own up to 50 GB, but every person who accesses it needs their own license. Features such as larger storage, an in-place archive or litigation hold require an Exchange Online Plan 2 license. In Google Workspace, a shared address is typically handled with groups or delegation, using your existing user accounts.
How many aliases can I have?
It depends on your platform. Google Workspace allows up to 30 aliases per user at no extra cost. On cPanel-based email, aliases are forwarders, which you can create as needed within your hosting plan's limits. Check your own plan's documentation for details.
Is it safe to share one email password with my team?
No. A shared password cannot be traced to a person, is hard to change without disrupting everyone, and stays in the hands of former staff until it is reset. Use aliases, forwarders, groups or shared mailboxes with individual logins and multi-factor authentication.
Should I use a catch-all email address?
Usually not. A catch-all delivers mail for every address that does not exist, which catches typos but also a flood of spam, including mail sent to guessed addresses. Most businesses are better off creating the specific addresses they need and rejecting the rest.
What is the best setup for a small team of five?
A practical starting point is one real mailbox per person, role addresses such as info@ and billing@ set up as aliases or forwarders to the right people, and a shared mailbox or shared inbox group for the address that gets the most customer conversations. Add multi-factor authentication, document who owns each address, and review access whenever someone joins or leaves.
Written by Beth Wangui
SteboHost engineering and operations team. We write practical guides on hosting, domains, email and security for African businesses — based on what we see in the field, not marketing copy.
Ready to get started?
Browse our hosting plans or contact our team for help choosing the right one.