Membership organizations, schools, clubs and charities all reach the same question eventually: should everyone have an address on our domain? The answer is usually yes and the reason it doesn't happen is cost, because email for every member priced per seat is unaffordable for any organization whose members aren't employees.
A choir with 200 singers, a professional body with 3,000 members, a school with 900 pupils — none of them can pay a monthly seat fee per person. This page covers what changes when they don't have to.
Why Organizations Want This
The motivation behind email for every member is rarely the email itself. It's what an address on the organization's domain represents.
Identity. A member address is a visible mark of belonging, and for professional bodies it's a credential of sorts — writing from the institute's domain says something a personal address doesn't.
Reachability that survives. Personal addresses change when people switch jobs or providers. An address on your domain doesn't, so the organization keeps a route to its members even when their personal details go stale.
A boundary. Volunteers using personal addresses for organizational business creates a mess when they stop volunteering. Email for every member keeps the correspondence on the organization's side of a line.
Continuity in roles. A committee position that carries its own address means the handover to the next holder is a change of access rather than a change of address, and nothing needs re-announcing.
The Cost, Honestly
At the $7 Google Workspace seat, email for every member across 900 pupils costs $75,600 a year, which is why schools don't do it. On plans that cap counts by tier rather than charging per mailbox, the same 900 addresses sit inside an Agency plan at $279 a year.
What you're really buying is storage, and that's where the planning goes. Agency provides 200 GB pooled, so 900 members works out at roughly 220 MB each. For an organization where members receive occasional announcements, that's ample for years. For a school where pupils exchange coursework attachments daily, it isn't, and the Drive add-on from $3.20 a month is the cheaper answer than a plan tier.
Per-mailbox quotas matter more here than anywhere, because a membership body has no control over what members do with their addresses. Setting a modest quota at creation prevents one enthusiastic member consuming the pool — the reasoning is in mailbox storage quotas.
Provisioning Without a Data Entry Project
Email for every member is only feasible if creation is one operation rather than hundreds, and if you never handle anybody's password.
Bulk creation takes a membership list and provisions the lot. Setup invites then let each member set their own password, which matters doubly here: you're dealing with people who aren't staff, whom you can't compel to follow a policy, and whose credentials you have no business knowing. The mechanics are in creating mailboxes in bulk.
The naming decision is worth making once and sticking to. First-name-surname works until two members share a name, which at 200 members is likely and at 3,000 is certain. Membership numbers are unlovely and unambiguous; a hybrid is usually the compromise organizations settle on.
Three Predictable Failures
Email for every member has three predictable problems, all worth planning for rather than discovering.
Members don't use it. This is the most common outcome and the least discussed. People have an email address they like and no appetite for a second one. Email for every member becomes hundreds of unopened mailboxes, and mail sent to them reaches nobody, which is worse than not having them.
The fix is forwarding rather than mailboxes for anyone who wants it — the address exists, mail reaches them where they already read, and the organization keeps its route. That needs a paid plan, since forwarding isn't available on the free tier.
Departures aren't handled. Members leave, students graduate, volunteers stop volunteering. Without a policy the addresses accumulate forever and the count becomes meaningless. Decide the retirement rule when you decide the naming scheme.
Somebody misuses the address. An address on your domain sending something objectionable is your reputation, not theirs. Terms of use and the ability to suspend an individual mailbox are both necessary, and both are easier to introduce at the start than after an incident.
Roles Versus People
A distinction worth drawing, because organizations frequently want both and configure only one.
Member addresses belong to individuals and follow them for as long as they're members. Role addresses — treasurer@, membership@, safeguarding@ — belong to positions and outlive whoever currently holds them.
Role addresses are better as shared mailboxes with membership, so a handover is adding one person and removing another, with the whole history intact for the incoming holder. That's the pattern in a mailbox per project, applied to committee positions instead of jobs.
Getting this wrong in the obvious direction — making the treasurer's address a personal mailbox — means every handover involves either sharing a password or losing the history, and organizations do it constantly.
What Happens When Membership Ends
Students graduate, members lapse, volunteers stop volunteering — and every one of those addresses is still receiving mail the day after.
The decision worth making early is whether a departing member keeps the address, loses it, or keeps it in a reduced form such as forwarding to a personal address. Alumni associations frequently choose the third, because the address remains a link to the organization and costs almost nothing to maintain. What causes trouble is having no rule, at which point the count grows forever and nobody can say which addresses belong to current members.
Starting Smaller Than Everyone
Email for every member doesn't have to begin with every member.
Committee and role addresses first, which are few, high-value and immediately useful. Then whichever member group actually asked for it. Then everyone, once you know what the take-up looks like and what the storage does.
Since mailboxes aren't billed individually, this staging costs nothing extra and tells you what you'd otherwise guess — particularly the take-up rate, which is the number that decides whether the full rollout is worth doing at all.
