Do you need a new inbox, or an email group?

When your team says "we need a new inbox everyone can log into," what they usually need is an email group instead. The two sound the same but work very differently, and picking the right one saves you money, hassle, and a shared-password headache down the road. This tutorial sorts out the difference in plain English, so you can ask for exactly the right thing.

💡 The question we hear all the time

It usually sounds like this:

"Can we get a new inbox for volunteers@ourorg.org that the whole team can log into and check?"

It's a completely reasonable thing to ask for. But nine times out of ten, a brand-new inbox is not the right tool for the job — an email group is. They look almost identical from the outside, so it's an easy mix-up. Let's clear it up.

📥 What an inbox actually is

An inbox is a mailbox. It's one place where mail arrives and lives, with one login.

Think of it like the physical mailbox at the end of a driveway. Mail goes in, and whoever has the key opens it up to read what's inside. If five people need to read that mail, they're all reaching into the same box with the same key.

That "same key" part is where the trouble starts, but we'll get to that.

📣 What an email group actually is

An email group is not a mailbox at all. It's an address that takes any message sent to it and drops a copy into each member's own inbox.

Think of it like a phone tree, or a single letter run through a photocopier. Someone emails volunteers@ourorg.org, and Jane, Bob, and Maria each get their own copy in their own regular email — the one they already check every day. Nobody logs into anything new. Nobody shares a password. You add or remove people from the group in a few seconds.

In Google Workspace this is called a Google Group. (Microsoft 365 calls the same thing a distribution group.)

⚖️ "But we want everyone to see the mail" — here's the part people get wrong

This is the heart of it. When someone asks for "an inbox the whole team can log into," what they really mean is "we want several people to see this mail." That's a great goal. The mistake is thinking a shared login is how you get there.

Here's what each option actually looks like:

What people ask for — one inbox, one shared password:

flowchart LR
    J["👤 Jane"] --> K["🔑 one shared<br>password"]
    B["👤 Bob"] --> K
    M["👤 Maria"] --> K
    K --> I["📥 ONE inbox<br>everyone logs into"]

What usually works better — a group that fans mail out to everyone:

flowchart LR
    S["📨 Someone emails<br>volunteers@ourorg.org"] --> G{{"📣 Email group<br>volunteers@ourorg.org"}}
    G --> JI["📥 Jane's own inbox"]
    G --> BI["📥 Bob's own inbox"]
    G --> MI["📥 Maria's own inbox"]

The shared-login version causes real problems:

• Everyone shares one password. That's a security risk, and the day someone leaves the team you have to change it for everybody.
• You can't tell who's handling what. Two people answer the same email, or everyone assumes someone else has it and nobody does.
• Read/unread gets confusing. Bob marks a message read, and now Jane never sees it.
• It costs more. A real mailbox usually means paying for another user license.

The group version sidesteps all of that. Each person works from the inbox they already know, replies as themselves, and you manage who's in the group with a couple of clicks.

✅ When to use each one

A group covers almost every "we all need to see this" situation. But a real dedicated mailbox does have its place. Here's how to tell them apart:

Not sure which you need? Walk it down:

flowchart TD
    Q1{"Do several people need<br>to see these emails?"} -->|"No, just me"| P["📥 A personal inbox"]
    Q1 -->|"Yes"| Q2{"Does the mail need its own<br>stored archive, separate<br>from any one person?"}
    Q2 -->|"No — people just<br>need to see & reply"| G["📣 An email group"]
    Q2 -->|"Yes — it's really<br>its own mailbox"| D["📬 A dedicated mailbox"]

✉️ "But how do we reply from the group address?"

This is the question that makes people give up on a group and demand a real inbox — so let's settle it. You have two good options.

Option 1: Just reply from your own email (usually the best choice)

When a message lands in your inbox through the group, you can simply reply the way you always do. The sender gets an answer from a real, named person at your organization — and most people prefer that to a reply from a faceless volunteers@ address. For most teams, this is all you need. Don't overthink it.

Option 2: Send as the group address

Sometimes you do want replies to come from volunteers@ourorg.org — so it reads as coming from the organization, and replies stay tied to the group. Gmail can do this. Each person sets it up once:

1. In Gmail, click the gear icon → See all settings → Accounts and Import.
2. Under Send mail as, click Add another email address.
3. Enter the group address (e.g. volunteers@ourorg.org), keep Treat as an alias checked, and continue.
4. Gmail sends a verification code to the group so it can confirm you're allowed to use the address. A group owner or manager approves it. (Google's setup guide walks through a small group-setting tweak that lets the code come through — see the link below.)
5. From then on, when you write or reply, you can pick the group address from the From dropdown.

Official Google steps for sending as a group address: support.google.com/groups/answer/10309372

👩‍💻 How to set up a Google Group

The short version:

1. Go to groups.google.com and click Create group.
2. Give it a name and the email address you want (e.g. volunteers@ourorg.org).
3. Choose who can post to it and who can see it.
4. Add your team members as members.
5. Done — mail sent to that address now reaches everyone you added.

If your organization's Google Workspace is managed by an administrator, they may need to create the group for you, or grant you permission to make one. (If we manage your Workspace, just ask — we'll set it up.)

🪟 On Microsoft 365 instead?

The same two tools exist, just with different names:

• An email group is a distribution group (or a Microsoft 365 group).
• A shared mailbox several people work out of is a shared mailbox — and Microsoft's shared mailboxes are built to be opened by each person from their own account, no shared password needed.

The decision is identical: do people just need to see and reply (group), or does the address need to be a real, archived mailbox of its own (shared mailbox)?

🤙 Still not sure?

This is exactly the kind of small decision that's easy to get wrong and annoying to undo later. If you're staring at it unsure which one to ask for, call us. We'll help you pick the right tool the first time — and set it up for you if you'd like. CampaignHelp is here for you.