Shared mailbox vs user mailbox: what does a small business need?

Picture fictional Ironbark Plumbing in Ballarat. Maya owns the business, Ben prepares quotes and Leila covers the office 2 days a week. Customers should not need to know who is rostered before emailing for a quote. Maya's private management conversations should remain tied to her.

That points to 2 different jobs: a shared mailbox for the quotes lane and a user mailbox for Maya.

Keep the parts separate

A public email address is not automatically a mailbox, licence or login. Before choosing a setup, separate these parts:

• Public address: what a customer types, such as quotes@ironbarkplumbing.example.
• Mailbox type: a common mailbox or an individual user's mailbox.
• Licence or plan: what the provider requires for that mailbox and each person using it.
• Login and permissions: how each authorised person gets access and what they may read, change, delete or send.
• Storage and history: where received and sent messages are kept and who can see them.
• Ownership of work: who is responsible for the next reply, follow-up or handover.
• Delegation: whether another person may access an existing mailbox without sharing a password.
• From and send-as behaviour: which identity recipients see on outgoing mail and replies.

These details depend on the provider, plan and configuration. Licensing, permissions, storage, delegation, sent items, audit history, retention and send-as behaviour should all be checked rather than assumed.

If the immediate question is whether several people need access at all, start with business email for multiple users. If the team only needs another public address routed somewhere, compare an email alias with a shared mailbox.

Choose a shared mailbox for common work

A shared mailbox fits quotes@ironbarkplumbing.example because the work belongs to Ironbark Plumbing, not to Ben or Leila. Authorised staff may need to see the same history and continue the conversation during leave or after a staffing change.

The operating process still matters. Name 1 owner for the lane, decide who covers it, and define how the team marks a quote as claimed, waiting or complete. A shared mailbox does not necessarily provide assignment, collision warnings, service levels or help-desk reporting.

Do not give everyone permanent access by default. Use named accounts and the least privilege needed for each role. Shared passwords make access and offboarding harder to control.

Choose a user mailbox for 1 person's identity

A user mailbox fits maya@ironbarkplumbing.example when messages belong to Maya's individual role, relationships and employment lifecycle. It commonly has its own account, access and storage, with licensing determined by the provider and plan.

Provider-supported delegation may allow an authorised person to work in Maya's mailbox without using her password. The permissions, visible actions, sent items and removal process need separate checks. Forwarding and mailbox delegation solve different problems: forwarding changes where incoming mail goes, while delegation changes who may work inside a mailbox.

A named address can still be the wrong place for common work. If Ben receives every quote at ben@ironbarkplumbing.example, the business may need to recover access, history and unfinished work when he takes leave or leaves the company. Changing a public route handles future delivery only; it may not preserve or transfer copies already stored in Ben's mailbox.

For a wider naming decision, see when a business email should use a person's name.

Safe setup and offboarding checklist

Before relying on either mailbox type:

1. Name the business owner for each operational lane and the administrator responsible for access.
2. Give each staff member their own sign-in and only the permissions their role needs.
3. Confirm where incoming mail, sent items and relevant history are stored and retained.
4. Send a harmless test from an unrelated external account and confirm it reaches the intended mailbox.
5. Reply to the test and inspect the visible From and Reply-To identities. Receiving at quotes@ does not prove replies will be sent from quotes@.
6. Check the same path in the browser, phone and desktop apps the team uses.
7. Document offboarding: remove access, sessions, connected apps, rules and delegation; preserve required business history; reassign unfinished work.
8. Test continuity by removing a test user's access and confirming another approved person can still find and continue the common work.

Use fictional test messages, not customer records, invoices, credentials or sensitive job details. The result proves only the setup checked at that time.

Where a shorter address may fit

Mailbox type and public address length are separate decisions. If the chosen public address is awkward to say, type or print, a Short Mail account manager can check whether a shorter public .au address may forward to the inbox the business already uses. Fit, availability, eligibility, setup and provider compatibility are confirmed manually. Mailbox hosting, staff access, history, retention and outbound From behaviour are not implied by that check.

Contact Short Mail to check whether a shorter forwarding address may fit your existing inbox setup.