Both make the mailbox available. They behave differently once it’s there — and the difference matters more than most people expect.
| Automapping | Account mapping | |
|---|---|---|
| Appears as | Additional folder tree | Separate account |
| Desktop notifications | No | Yes |
| Full search across mailbox | Limited | Yes |
| Separate send-as identity | Manual selection | Native |
| Profile load impact | Minimal | Slightly higher |
| Group-based management | Yes, with SharedConX | Yes, with SharedConX |
The catch: no desktop notifications. If a team must respond quickly, automapping alone will frustrate them.
The trade-off: profile weight. A handful of mapped accounts is fine; twenty is not.
A practical rule: ask whether anyone is waiting for mail in that mailbox. If yes — account mapping. If it’s a reference or archive mailbox — automapping.
SharedConX supports Account Mapping and Auto-Mapping — but only one mode applies per mailbox at any given time. The mode is controlled by the same underlying security group, so you can switch approaches without touching the permission structure itself.