Guide Email

How to set up a shared mailbox for a team

Two ways to give a team a single email address to work from, and which one suits a small team versus a larger one.

iFastHosting Support Team Updated 26 August 2026 8 min read Intermediate

A shared mailbox — support@yourdomain.com, sales@yourdomain.com, and similar — needs to be readable and answerable by more than one person without everyone stepping on each other's replies or losing track of what has already been handled. There are two workable approaches, and which one suits you depends mostly on team size.

Option 1: one shared mailbox, everyone connects to it

Create a single mailbox and give every team member its login details. Because IMAP keeps mail on the server, everyone connecting to the same account sees the same inbox in real time — a message marked as read by one person shows as read for everyone else too, and a reply sent by one person is visible to the rest of the team through the shared Sent folder.

Create the mailbox
Set it up in the email section of your control panel exactly as you would any other address.
Share the credentials securely
Use a password manager with shared access, rather than emailing or messaging the password in plain text where it can linger indefinitely in a chat history.
Have each person add it to their mail app using IMAP
See setting up email on your domain for the general settings, and the client-specific guides for the app each person uses.
Agree how the team signals a message is being handled
A simple convention — moving a message to an "In Progress" folder, or using a specific flag or label — avoids two people replying to the same enquiry independently.

	Best for
Shared mailbox with one login	Small teams who trust each other with one shared password and want a genuinely single, synced inbox
Forwarder to individual mailboxes	Larger or more distributed teams, where individual accountability for replies matters more than one shared password

Option 2: a forwarder feeding individual mailboxes

Instead of one shared login, create a forwarder that copies mail sent to the shared address into each team member's own personal mailbox. Everyone sees incoming mail without a shared password to manage, but replies come from each person's own address rather than the shared one unless they are separately configured to send as it, and there is more risk of duplicate replies without a clear process for claiming a message.

Forwarding does not give you a shared view of who replied

Because each person's copy lives in their own separate mailbox, there is no single place showing what has already been answered, unlike a genuinely shared mailbox. This works fine for a very small, well-coordinated team, but becomes harder to manage as the team or the mail volume grows.

Adding an autoresponder

A shared support-style address often benefits from an automatic acknowledgement confirming a message was received, separate from the eventual personal reply. See setting up an out-of-office autoresponder — the same feature works for an initial "we've received your message" reply as well as an away notice.

Managing access as the team changes

When someone leaves the team or changes role, change the shared mailbox's password immediately and update it for everyone who still needs access — the old password should not continue working for someone who no longer needs it. See changing an email account password. This is one of the practical advantages of the forwarder approach: removing one person's access is as simple as removing their address from the forwarder's destination list, with no password to change for everyone else.

Keeping the inbox organised

Create folders for common categories, which every team member sees since they are stored on the server.
Archive or file handled messages out of the main inbox view, so what remains is genuinely still open.
Review the mailbox's storage usage periodically — a busy shared address can approach its quota faster than an individual one.

Either approach is a reasonable starting point, and it is entirely possible to start with forwarding for a very small team and move to a genuinely shared mailbox later as volume grows and the coordination overhead of separate inboxes starts to show.

Sending consistent replies as a team

If several people reply from the same shared mailbox, agreeing a simple shared signature and a consistent tone helps the address feel like it belongs to the business rather than to whichever person happened to answer that day. This matters more for an address customers write to repeatedly, such as a support inbox, than for a low-volume address only used occasionally.

Setting up an autoresponder for the shared address

Beyond an away notice, a shared mailbox used for enquiries benefits from an immediate automatic acknowledgement confirming a message has been received, with an indication of expected response time. This sets expectations for the sender and reduces the number of "did you get my email" follow-ups the team has to deal with separately. See setting up an autoresponder for how to configure this.

Do not let a shared password go stale

A shared mailbox's password is only as secure as the least careful person who has ever had it. Change it periodically as a matter of routine, not just when someone leaves, particularly if it has ever been shared through a channel — an old chat message, a printed note — that is not properly access-controlled.

Whichever approach you choose, the underlying mailbox is set up exactly the same way as any other address on your domain — see setting up email on your domain for the general process if you have not created a mailbox before.