πŸ“§
E-mail

Create a Shared Mailbox for Your Team

πŸ“… 10 October 2026 ✏️ 10 October 2026 ⏱ 5 min leestijd

Learn step by step how to set up a shared mailbox for your team in Plesk, including permissions and practical tips for daily use.

A shared mailbox is an email address such as [email protected] that multiple colleagues can access, without everyone needing a separate password or individual account. You create it through the email management of your hosting package, assign users, and set permissions. Below you’ll find exactly how to do this and what to watch out for regarding management and security.

What is a shared mailbox and when do you use one

A shared mailbox is a mailbox managed by multiple people at once, for example info@, support@, or sales@. Instead of every employee having their own mailbox and forwarding emails, colleagues log in to the same mailbox or add it as a shared folder in their email program. This prevents customer emails from being left unanswered because one person is unavailable, and provides overview: everyone sees the same incoming and answered messages.

Shared mailboxes are especially useful for customer service, sales, job applications, or a general contact address. For roles where one person is responsible, such as a management address, a regular mailbox often makes more sense. Want more background on how business email works? Check out the page about business email.

[email protected]Colleague AColleague BColleague CPlesk management

Creating a shared mailbox in Plesk

At Tandata, you manage email through Plesk, the control panel included with your web hosting. Creating a shared mailbox is technically the same as creating a regular mailbox: you simply choose a name that corresponds to a function rather than a single person.

1

Log in to Plesk

Open your Plesk environment and go to the ‘Email Addresses’ or ‘Mail’ section for the relevant domain.

2

Create a new email address

Choose a functional name such as info@, support@, or sales@ followed by your domain name. Avoid personal names so the mailbox remains recognizable as a team address.

3

Set a strong password

Use a unique, long password and store it in a secure, shared location for the team members who need to log in.

4

Set the storage limit

Give the mailbox enough space, especially if there are many messages and attachments coming in. Thanks to NVMe storage, you won’t notice any slowdown even with larger mailboxes.

5

Add the mailbox in mail clients

Have each colleague add the mailbox via IMAP, so that read and answered messages show the same overview for everyone.

Granting access and setting permissions

There are two ways to give a team access to the same mailbox. The simplest is for everyone to log in using the same account and password via IMAP. This works well for small teams, but has the downside that you can’t see who performed which action, and you need to change the password whenever staff changes occur.

A cleaner solution is to work with forwarding or delegation: incoming mail on the shared address is automatically forwarded to team members’ personal mailboxes, while mail sent from the shared address is done using a configured sender address (alias) in each person’s own mail client. This keeps it clear who is responding, while customers still see one fixed address.

Choose the method that fits your team’s size and the level of control you need. For a small team, direct IMAP access is often sufficient; for larger departments, delegation provides more clarity.

πŸ’‘ Tip: Agree within the team on how to mark read messages, for example with labels or folders, so no one answers the same customer twice.

Management, security, and common mistakes

A shared mailbox requires a bit more attention than a personal mailbox, since multiple people have access. Make sure passwords are changed periodically, especially after an employee leaves. Use strong authentication where possible and limit the number of people who actually know the password.

Also pay attention to the technology behind your email. A correctly configured SPF, DKIM, and DMARC setup ensures that messages from the shared mailbox aren’t flagged as spam. Tandata mailboxes are set up by default to achieve a full score on internet.nl, which benefits your email deliverability.

Common mistakes include: giving too many people access without oversight, not agreeing on who responds, and forgetting to link the mailbox to a properly functioning domain. If in doubt, also check whether your domain name is correctly linked to your hosting package, otherwise mail won’t arrive.

Frequently Asked Questions

Can I later convert a shared mailbox into a regular mailbox?

Yes, that’s possible without data loss. You just adjust the settings and access rights; existing emails remain intact.

How many people can log in to one shared mailbox at the same time?

This depends on your mail client and settings, but multiple simultaneous users via IMAP is usually not a problem.

Can I see who replied to a message from the shared mailbox?

Not by default with direct IMAP access. If you want to track this, opt for delegation with personal sender addresses or note it manually in the message.

Is a shared mailbox just as secure as a regular mailbox?

Yes, provided you manage access properly. Limit the number of users, use strong passwords, and change them whenever staff changes occur.

Can I bring my existing shared mailboxes with me when switching to Tandata?

Yes, when switching to Tandata, we help you migrate your mailboxes and settings without losing any mail.

Conclusion

Setting up a shared mailbox is quick and easy in Plesk: you create a functional email address, set a strong password, and connect the mailbox for each team member via IMAP. Choose direct access for small teams, or delegation when you want more oversight over who’s responding. Keep security in mind by changing passwords whenever staff changes occur, and make sure your domain is correctly configured for reliable deliverability.

View web hosting β†’

Was dit artikel nuttig?