Structure departmental email around three building blocks — an individual mailbox for every person, an alias for any department address that simply routes to someone, and a shared or group address for functions a team handles together. Verify your domain, publish SPF, DKIM, and DMARC, decide a naming convention before creating anything, then assign admin roles on the principle of least privilege. NevTan Mail includes unlimited aliases and groups, so department addresses do not each consume a paid mailbox.
This guide covers planning the structure first, then the setup.
Why Structure Matters Before Setup
Most departmental email problems are structural, not technical. They come from creating addresses reactively — someone needs billing@, so a mailbox gets made — until nobody can say which addresses exist, who owns them, or what happens when the owner leaves.
A deliberate structure does three things. Customer messages reach a destination that outlives any individual. Internal announcements go to a defined group rather than a copied-and-pasted list. And access to sensitive correspondence is controlled by role rather than by who happens to know a password.
There is a credibility dimension too. A company answering from sales@, support@, and billing@ reads as organized in a way that john.personal@gmail.com does not — the trust argument covered in why every business needs a professional email address.
The Three Building Blocks
Getting this distinction right determines both your costs and whether the setup works. It is the single most useful thing in this guide.
Individual mailbox | Alias | Group | |
|---|---|---|---|
What it is | A person's account with its own login and storage | An extra address routing to an existing mailbox | An address delivering one message to several members' own inboxes |
Storage | Its own | None — mail lands in the target mailbox | None — copies land in members' mailboxes |
Best for | Every employee |
| Announcements, internal notifications, escalation routing |
Cost | Consumes a paid mailbox | Free on NevTan Mail | Free on NevTan Mail |
A fourth pattern — the shared mailbox, where several people work one inbox with shared history, shared sent items, and send-as permission — behaves differently from a group. A group distributes mail to individuals; a shared mailbox holds it centrally so a team can work it together with no duplicate replies. If you are choosing between them for a support queue, the distinction matters more than any other decision in this guide, and it is worth reading up on before you build.
Practical rule: if a person needs to send as themselves, they need a mailbox. If an address just needs to reach someone, use an alias. If a message needs to reach many people, use a group. If a team needs to work an inbox together, you want a shared mailbox specifically — confirm your provider supports it as distinct from a group.
Before You Start
A custom domain, plus access to its DNS. You will add TXT and MX records.
A naming convention, written down. first.last@ for people, department@ for functions. Decide before creating a single account — changing it later means updating signatures, invoices, business cards, and every third-party tool.
A department and headcount list. Who belongs to which team, and which shared addresses each needs. This is your build sheet.
App passwords at your current provider, if migrating. NevTan Mail imports existing mail from Google, Yahoo, or Zoho over IMAP using an app password you generate there — standard credentials will not work with two-factor authentication enabled.
Step 1: Verify Your Domain and Configure DNS
Add your domain in the admin area and publish the TXT record it generates to verify ownership. Verification typically completes within minutes, though propagation can take up to 48 hours.
Then configure mail routing and authentication:
MX records direct incoming mail to your provider. Remove old MX records from your previous provider — leaving them in place causes intermittent, hard-to-diagnose routing failures.
SPF authorizes every service that sends as your domain. Note the hard limit of 10 DNS lookups; each CRM, invoicing tool, and marketing platform consumes some, and exceeding the limit fails permanently rather than gracefully.
DKIM signs your outgoing mail.
DMARC starts at
p=noneso you can see who sends as your domain, then tightens top=quarantineandp=rejectonce legitimate senders are confirmed.
NevTan Mail's guided setup generates and verifies each record. For what each does, see domain authentication and why business emails land in spam.
💡 Pro Tip: Keep your DNS console and mail admin open in separate tabs to copy values across without losing your place. Verify each record before moving to the next rather than adding all four and debugging afterwards.
Step 2: Create Department Aliases
Aliases are department addresses that route to existing mailboxes. They are the reason a 20-person company does not need 30 mailboxes.
Create one per customer-facing function and point it at whoever currently owns that function. sales@ routes to the sales lead. billing@ routes to finance. The address stays constant for customers even as the person behind it changes — which is the entire point.
Because NevTan Mail includes unlimited aliases, this costs nothing. Aliases also work well for temporary needs: a conference address, a campaign address, a vendor-specific address you can retire later.
💡 Pro Tip: Set up the standard four —
sales@,support@,billing@,hr@— even as a small team. They cost nothing, they make you easy to contact correctly, and they mean you are not re-architecting when you hire.
Step 3: Set Up Shared and Group Addresses
For functions a team handles together, a single routing address is not enough. Support and sales queues need visibility: who replied, what was said, whether a message was handled.
Groups distribute a message to each member's own inbox. Right for announcements, on-call alerts, and internal notifications where the goal is that everyone sees it.
Shared mailboxes hold mail centrally so a team works one inbox with common history. Right for support@ where three agents share a queue and duplicate replies are the failure mode.
The distinction is easy to blur during setup and expensive to discover afterwards. If your support address is a group, every agent gets a private copy and nobody knows who answered. Confirm which model your provider offers before you route customer mail through it, and check whether shared access includes send-as permission and a shared sent-items folder.
💡 Pro Tip: Whichever model you use, agree a claiming convention before go-live — assigning, flagging, or replying-all to signal ownership. Visibility solves who can see a message; it does not solve who will answer it.
Step 4: Assign Admin Roles
Not everyone should be able to delete the company's email.
NevTan Mail uses role-based access with Admin and Super Admin roles, governing who manages domains, mailboxes, and billing. Assign Super Admin narrowly — typically one or two people — and Admin to whoever handles day-to-day user management.
Apply least privilege: people get the access their job requires and no more. This limits the damage from a compromised account and makes offboarding a defined action rather than a scramble.
If you need finer-grained delegation than your provider offers — say, a department head managing only their own team's mailboxes — confirm what is actually supported before designing your structure around it. Delegation models vary considerably between providers and are frequently described in vaguer terms than they are implemented.
💡 Pro Tip: Audit admin access quarterly. Review who holds elevated rights and revoke it for anyone who changed roles or left. Lingering admin accounts belonging to former staff are a standard finding in security reviews.
Step 5: Onboard Your Team
Create individual mailboxes for each person following your naming convention, then assign them to the relevant groups and shared addresses.
Where your provider supports it, prefer an invitation flow that has the user set their own password over an administrator-set temporary one — fewer people know the credential, and it avoids passwords being shared over chat.
For migrations, NevTan Mail imports existing mail from Google, Yahoo, or Zoho over IMAP using an app password. Run a pilot with a few users before moving everyone, and keep the old provider active for at least 30 days afterwards. See the Gmail migration walkthrough.
💡 Pro Tip: Write a one-page onboarding checklist — signature format, which shared addresses they belong to, how to flag a claimed thread, and who to contact for access. Fifteen minutes on day one prevents months of inconsistency.
A Worked Example
Acme Analytics has 50 employees across Sales (10), Support (8), Engineering (15), Marketing (5), and HR/Finance (12). They are running on a mix of personal accounts and one overloaded shared inbox.
Domain and DNS. They verify acmeanalytics.com, publish MX, SPF, DKIM, and DMARC at p=none, and remove the old MX records. About 30 minutes of work, then two weeks of watching DMARC reports before tightening — during which they discover their invoicing platform was never in SPF.
Mailboxes. Fifty individual mailboxes, one per employee. On NevTan Mail's Growth package at $2 per mailbox per year with 35 GB each, that is $100 for the year. Ten of those would be free on the entry tier, but 50 people needs a paid package. Compare against per-seat providers at $72 and up per user annually and the gap is the point.
Aliases. info@, careers@, billing@, press@ — routing to the relevant owners. No additional mailboxes consumed.
Team addresses. support@ and sales@ are the two that need genuine team access, since multiple people work each queue and duplicate replies would reach customers. These get set up as shared team inboxes rather than simple distribution, and each team agrees a claiming convention before go-live.
Admin. The CTO and Head of Operations are Super Admins. The office manager gets Admin for day-to-day user creation. Nobody else has elevated rights.
Migration. They pilot with four people, confirm folders and calendar data arrived, then move the rest in batches. The old provider stays live for 30 days.
Total: roughly a week end to end, with the DMARC observation window running in parallel.
Choosing Your Structure by Size
Team size | Typical structure |
|---|---|
Under 10 | Individual mailboxes, 2–4 aliases. Shared inboxes usually unnecessary — you all see everything anyway |
10–50 | Individual mailboxes, aliases per function, shared inboxes for support and sales, Admin/Super Admin split |
50–200 | The above plus formal quarterly access audits, defensive naming standards, and documented offboarding |
200+ | Evaluate identity-provider integration and delegated departmental administration explicitly — confirm support rather than assuming it |
Five Common Mistakes
1. Running business mail on personal accounts. When someone leaves, the conversations leave with them. No admin control, no authentication control, no ownership.
2. Creating a mailbox for every address. info@, hello@, and contact@ do not need three mailboxes. Aliases cost nothing and keep the user list clean.
3. Making everyone an admin. Least privilege exists because compromised accounts and honest mistakes both happen. Industry breach reporting consistently finds the human element involved in the large majority of incidents, and limiting access limits the damage.
4. Skipping authentication. Without SPF, DKIM, and DMARC, departmental mail lands in spam — and sales outreach suffers first. Since 2024, Google and Yahoo have required authentication from bulk senders, with Microsoft following in 2025.
5. Letting people pick their own addresses. You end up with dave@, david.k@, and dkowalski@ for one person. Standardize before the first account exists.
Frequently Asked Questions
How do I create a department address like sales@mycompany.com?
Create it as an alias pointing to whoever owns that function, or as a shared team inbox if multiple people work the queue together. An alias requires no separate mailbox and no additional cost on NevTan Mail.
Can multiple people manage one support inbox?
That depends on whether your provider offers shared mailboxes with delegated access as distinct from distribution groups. A shared mailbox gives the team one inbox with common history and send-as permission; a group delivers separate copies to each member. For a support queue you want the former — verify which your provider supports before routing customer mail through it.
What is the difference between an alias and a group?
An alias routes an address to an existing mailbox, with no separate storage. A group delivers a copy of each message to every member's own inbox. Neither stores mail centrally — for that you need a shared mailbox.
How many aliases can I create?
NevTan Mail includes unlimited aliases and groups, so department, project, and campaign addresses do not consume paid mailboxes.
How do I set different admin permissions for department heads?
NevTan Mail provides Admin and Super Admin roles. If you need departmental scoping beyond that — a head of engineering managing only their team — confirm what your provider supports before building your structure around it.
Can I migrate my whole team from Gmail?
Yes. NevTan Mail imports mail from Google, Yahoo, or Zoho over IMAP using an app password generated at your current provider. Pilot with a few users first, then migrate in batches, keeping the old provider active for 30 days.
Should I set up a catch-all address?
Catch-alls capture mail sent to non-existent addresses on your domain, which prevents typo bounces but attracts substantial spam. If your provider supports one, treat it as a monitored net rather than a real address, and never use it for customer-facing contact.
How many mailboxes will I actually need?
One per person, plus one per function a team genuinely works together. Everything else can usually be an alias. For most companies that means headcount plus two or three, not headcount plus ten.
Conclusion
Departmental email is an exercise in matching structure to function. People get mailboxes. Routing addresses get aliases. Broadcast addresses get groups. Queues a team works together get shared inboxes. Admin rights go to the few who need them.
Decide the naming convention and the structure before creating a single account, because retrofitting is far more painful than planning. Get the authentication records right at the same time, so departmental mail reaches inboxes from the start.
NevTan Mail supports this with business email on your own domain, unlimited aliases and groups, role-based admin controls, guided SPF, DKIM, and DMARC setup, calendar and meetings in the inbox, and no ads or data selling on any plan. Ten mailboxes with 5 GB each are free forever, so you can build and test the structure before spending anything.
Get started free, see current pricing, or read what NevTan Mail includes end to end.
