Email forwarding vs mailbox delegation: which fits a small business?
Use forwarding when incoming mail only needs to move from a public address to an inbox someone already owns. Use mailbox delegation when an authorised staff member needs controlled access to an existing mailbox and its stored history. Forwarding changes the route. Delegation changes who can work inside the mailbox. Neither choice automatically controls the outgoing From address, Reply-To address, retained copies or every permission.
Picture fictional Harbour Spark Electrical in regional Victoria. Owner Alex has used alex@harbourspark.example for years. The business hires office administrator Priya to handle incoming enquiries and accounts mail. Should accounts@harbourspark.example forward somewhere, or should Priya receive delegated access to Alex’s existing mailbox?
Start with the 7 parts of the setup
These terms describe different parts of the email path:
- Address: what a customer or supplier types, such as
accounts@harbourspark.example. - Forwarding route: a provider-supported rule that sends incoming mail from that address to another destination.
- Destination mailbox: where forwarded mail is stored and opened, such as
alex@harbourspark.example. - Delegated access: provider-supported access that may let Priya open or work in Alex’s mailbox without using Alex’s password.
- Permissions: what Priya may read, change, delete or send, subject to the provider, plan and configuration.
- Storage and history: where incoming and sent messages are retained, for how long, and what each authorised user can see.
- From and Reply-To: the addresses a recipient sees on outgoing mail and uses when replying. Incoming forwarding or delegated access does not prove either field will show
accounts@harbourspark.example.
If several public addresses may lead to the same inbox, first separate each address from its route and destination mailbox. An address is not a login, and a route is not a permission.
When forwarding is the smaller fit
Forwarding may be enough if Alex still owns every conversation and Priya only monitors a separate destination mailbox assigned to her. For example, accounts@harbourspark.example could forward to office@harbourspark.example, provided that destination and access arrangement are approved and tested.
It is a weaker fit if the route sends business mail into Priya’s personal or individually owned inbox. Alex may not see Priya’s filing, drafts or sent messages. When Priya leaves, changing the forwarding destination stops future delivery to that route, but it may not remove copies already stored elsewhere. The business must confirm what remains and who controls it.
Forwarding also does not give Priya access to mail already stored in Alex’s mailbox. If history matters, routing new messages alone does not solve the job.
When delegation is the better fit
Delegation is worth investigating when Priya needs to work from Alex’s existing mailbox, see relevant history and hand work back without sharing Alex’s password. Depending on the provider and permissions, Alex may retain mailbox ownership while Priya receives authorised access.
Check the scope carefully. Can Priya read all folders or only selected mail? Can she delete or move messages? Can she send, and if so, which From address appears? Are sent items visible to Alex? Is there an audit record? What retention rules apply? Delegation, licensing, send-as, sent-items, audit and retention behaviour vary by provider, plan and setup.
When Priya changes role or leaves, an administrator should be able to remove her access, check connected apps or active sessions, review forwarding rules and preserve the business history required. Do not assume removing 1 permission completes every offboarding step.
This is different from a team needing a common queue, shared assignment or collision controls. That wider choice belongs in shared mailbox vs email forwarding. The decision here is narrower: who may access 1 existing mailbox, with which permissions, and what must happen when that access ends.
Decision checklist
Choose the setup only after answering these questions:
- Does incoming mail merely need a new route, or must Priya work in existing mailbox history?
- Which mailbox stores the business record?
- Exactly what may Priya read, change, delete or send?
- Can Alex see Priya’s actions and sent messages where required?
- What access, sessions, rules and stored copies must be removed or retained during offboarding?
- Which From and Reply-To addresses should suppliers and customers see?
- Does the current provider and plan support that behaviour?
If the underlying question is whether to add another identity or another storage destination, compare an email alias with a mailbox. If replies should show the public address, check the separate reply-from and forwarded-address setup.
Test before relying on it
Use harmless fictional messages from an unrelated external account. Confirm delivery, destination, visible recipient, authorised access, storage and any expected source copy. Start a test reply and inspect From and Reply-To. Check where sent mail appears. Then remove the test delegate and confirm access is gone before restoring only the approved setup.
Repeat the test in the browser, phone and desktop apps the business uses. Do not use customer details, invoices, credentials or sensitive job information. A successful test proves only the path and permissions tested at that time.
Where Short Mail may fit
If the public address is hard to say, type or print, a Short Mail account manager may check whether a shorter matched .au address can forward to the inbox the business already uses. Fit, availability, eligibility, setup requirements and provider compatibility are confirmed manually. Sending and reply behaviour are confirmed separately.
Contact Short Mail to check whether a shorter forwarding address may fit your existing inbox setup.