topicsidentity & access3 numbers3 guides

shared mailboxes

The address belongs to a function, so nobody takes anyone off it. Whoever can read info@ today can reset every tool registered to it.

in one lineA shared mailbox is a role address such as info@ or invoices@ that several people read and send from, either with their own logins or with one password they all know.

the numbers

all the numbers →

1what it is

Every company has addresses that belong to a function: info@, invoices@, support@, careers@. They go on the website and supplier forms, and become the sign-in or recovery address of tools registered with them.

A role address gets built in one of two ways:

  • An ordinary user account with a shared password. Everyone signs in as info@. This is the shared admin account pattern applied to mail: one identity in the log, MFA on one person's phone, one password to change whenever anyone leaves.
  • A mailbox people open with their own login. In Microsoft 365 this is a shared mailbox, reached through permissions granted to each person's account. In Google Workspace it is a group used as an inbox or a Gmail account with delegates.

Microsoft's page on shared mailboxes says one is not meant for direct sign-in and tells admins to block sign-in for its account and keep it blocked. The same page says a shared mailbox holds up to 50 GB without a licence, so the licence fee is no reason to run info@ as a user. Product settings are in the shared mailbox guide; one leader's mailbox handed to an assistant is in the assistant delegation guide.

2why it accumulates

Joining is a request and leaving is nothing. Someone joins finance and asks for invoices@. When they move to sales, nobody files a request to take it back, and the permission stays until someone removes it. The stayers guide follows how access piles up when people change roles without leaving; a role mailbox is one place it collects.

Groups hide the names. Microsoft's Exchange permissions page says Full Access can be granted to a mail-enabled security group. The mailbox then lists the group, and the people who can read it are whoever is in that group today. Google's delegation page says a Google group can be a delegate if the admin allows it, and that one Gmail account supports up to 1,000 delegates.

Group archives start wide. Google's organisation-wide groups policy page (updated 10 November 2026) lists all organisation users as the default for who can view a group's conversations, and says that changing most of these defaults affects only groups created afterwards.

A leaver's mailbox can become one. Microsoft's conversion page says that if the password is not reset, the original username and password keep working on the converted shared mailbox, and that inbox rules are preserved. A colleague gets the mail, and a forwarding rule the former employee set up travels with it. The mail layer guide explains why such rules are easy to miss.

The shared password outlives the people who learned it. Changing it means telling everyone who stays, so it gets put off. The shared vaults guide covers why a password someone has seen should be treated as known.

3what it costs you

Every reset link lands there. A "forgot password" button sends a link to the address on file. When that address is invoices@, the accounting tool, the parcel carrier account or the domain registrar belongs to whoever reads invoices@ when the link arrives.

Payment mail lands there too. Supplier invoices and bank detail changes arrive in the same inbox. The FBI's IC3 2025 Internet Crime Report counts 24,768 business email compromise complaints with reported losses of about $3.05 billion, and describes the scam as compromising email and other communication to get funds transferred. The report does not say how many of those went through a shared mailbox. The payment approval guide covers what to do with a changed bank account.

The record gets thin. Microsoft's mailbox auditing page says auditing is on by default for shared mailboxes and records a person holding Full Access or Send As as a delegate. With a shared password, every action belongs to info@ itself. Outside the company, Microsoft's permissions page says a message sent with Send As carries no indication of which delegate sent it.

Anyone on the list can make a message disappear. Microsoft's shared mailbox page says you cannot prevent members from deleting messages in a shared mailbox. For invoices@, that includes the supplier's email about new bank details.

what it looks like when it goes wrong

Three ways this tends to go, each one taken from a real case.

your company
the gap nobody seesPeople are added to a shared inbox when they join a team, and nobody removes them when they move on or leave.access that outlives the job
  1. howThe person logs back in from home, weeks after leaving.
    what leavescustomer lists and reportswho ends up with itthe former employee and whoever they work for next
    it happenedCash App / Block, 2022
  2. howThe forgotten account's password turns up in a breach dump.
    what leavesa working way into the networkwho ends up with ita ransomware crew
    it happenedColonial Pipeline, 2021
  3. howA key or token set up for old work keeps working after everyone forgets it.
    what leavesinternal systems and documentswho ends up with itwhoever tries the key first
    it happenedCloudflare, 2023

4what works

  1. List every role address and how it is built. A user with a password, a shared mailbox, a group or a delegated account.
  2. Export the reader lists. Full Access and Send As in the Exchange admin center; members and who can view conversations for Google groups; delegates for Gmail accounts. Open every security group that appears and read its members too.
  3. Close the shared password. Block sign-in for any role address that is an ordinary account, or convert it to a shared mailbox, then change the password. For a converted leaver's mailbox, reset the password and read its inbox rules.
  4. Give each address one named owner. They approve who is added. The ownership guide explains why that person probably already exists.
  5. Write down what each address controls. Search the inbox by subject for password reset and welcome emails. For the registrar and the bank portal, consider an address with a few named readers.
  6. Put role addresses on the leaver and mover checklists. Removing someone's own account leaves their place on invoices@ untouched. The offboarding explainer covers the rest of that checklist.

Who on the invoices@ list today would you hand the password to your accounting tool?

on the record

← all topics

your turn

what you can do about it

  1. this week

    Export who has Full Access and Send As on every shared mailbox, and the members of every group or delegated account used as an inbox.

    Remove anyone who no longer works on that function. Any role address that is an ordinary account with a password people know gets its sign-in blocked and its password changed.

  2. go deeper

  3. if you're not sure where to start

    Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.

    open the checklist →

the letter · every two weeks

one access gap in your inbox, with the fix.

Every issue takes one way access creeps in, shows a real incident where it went wrong, and ends with one thing to check that week. Written for the people who run the tools, without a security team behind them.

  • 1one mechanism, explained plainly
  • 2one real incident, taken apart
  • 3one step you can take on Monday

get the next issue

One email every two weeks. Your address stays here and is never passed to vendors. One click to unsubscribe. Privacy.