in this guide
  1. two ways to build info@
  2. what the log can tell you afterwards
  3. the reset link is the door
  4. the inbox nobody offboards
  5. what a clean setup looks like
  6. questions the list will raise

Every company has a few addresses that belong to nobody: info@, invoices@, support@, hello@. They go on the website, on supplier forms and on the sign-up page of whatever tool somebody needed on a Tuesday. Then they start collecting things. Invoices with bank details. Renewal notices. And the password reset link for every account that was registered with them.

That last item is the mechanism. A “forgot password” button sends a link to the address on file. When the address on file is a shared inbox, the account belongs to whoever can read that inbox at the moment the link arrives. So the reader list of info@ is the real access list for every tool registered to it. Could you write that list down from memory?

This guide pairs with the mail layer guide, which looks at delegation and forwarding on personal mailboxes in Google Workspace, and with the shared admin accounts topic, which covers one login used by several people. The shared inbox sits where the two meet. It is a mailbox, and in some companies it is also a shared login. Handing one leader’s mailbox to an assistant is a separate case, covered in the assistant delegation guide.

The shared mailboxes topic has the short version and the numbers.

two ways to build info@

A shared inbox gets built in one of two ways, and the choice decides almost everything that follows.

An ordinary user account with a password several people know. Someone creates info@ as a normal user, gives it a licence and passes the password around: in a vault, in a chat message, on a note at reception. Everyone signs in as info@. This is the shared admin account pattern applied to mail.

A shared mailbox, group or delegated account that people open with their own login. In Microsoft 365 this is a shared mailbox. In Google Workspace it can be a group used as a collaborative inbox, a Gmail account with delegates, or the shared inbox an administrator creates. Each person reaches the mail through their own account, with their own MFA.

Microsoft’s documentation is clear about which one it intends. Its page on shared mailboxes says a shared mailbox is not meant for direct sign-in, and tells admins to block sign-in for its account and keep it blocked. Every shared mailbox has a user account behind it with a system-generated password that, in Microsoft’s words, “isn’t known or intended for use”. The page on creating one says new shared mailboxes have sign-in blocked by default. The same documentation says a shared mailbox can hold up to 50 GB without a licence, so in Microsoft 365 the licence cost is no argument for the first pattern.

Google offers three routes. Its delegation page says delegates can read, send and receive mail on behalf of the account owner, that one Gmail account supports up to 1,000 delegates, and that delegation works only between users in the same organisation. Its group settings let owners decide who can view conversations and who can post from the group’s address. And Google’s admin help describes a shared inbox that an administrator creates and grants to users, on Business Starter, Standard and Plus, which the page (updated 10 November 2026) says is being released in phases.

the same address, built two ways

a shared password

everyone signs in as info@

  • The log shows info@ did it
  • MFA sits on one person's phone
  • Removing one person means a new password for all
  • Whoever leaves still knows it

personal logins, shared mailbox

each person opens it as themselves

  • The log records the person as a delegate
  • Each person has their own MFA
  • Removing one person is one click
  • Disabling the leaver ends their access

what the log can tell you afterwards

The difference shows up on the day something goes wrong in that inbox.

Microsoft’s documentation on mailbox auditing says it is on by default, shared mailboxes included. Every recorded action is filed under one of three sign-in types: owner, delegate or admin. A person who holds Full Access, Send As or Send on Behalf on a mailbox counts as a delegate. For delegates, the default set logs sending as or on behalf of the mailbox, deleting messages, changing inbox rules and mail access.

When everyone signs in as info@ with the shared password, every action is the owner’s. The log can tell you that info@ deleted the supplier’s email about new bank details. It cannot tell you which of the people who know the password did it.

People outside the company cannot tell either. Microsoft’s permissions page says a message sent with Send As carries no indication of which delegate sent it, while Send on Behalf shows the person’s name next to the mailbox. Both are reasonable choices for a team address. Pick one on purpose, and know that with Send As the audit log is the only place the real sender is recorded.

One more line from Microsoft’s shared mailbox page belongs on the list: you cannot stop members from deleting messages in a shared mailbox. Microsoft points to a Microsoft 365 group if deletion has to be restricted. For an invoices address, that means anyone on the reader list can make a message disappear, and the log is the only trace.

The inbox matters because of what it can open.

how a role address becomes a login

  1. 1registered years agoA tool, portal or page is set up with invoices@ as login or recovery.
  2. 2forgot passwordAnyone can press the button on the tool's sign-in page.
  3. 3the link lands in the shared inboxEvery reader of invoices@ can see it.
  4. 4a reader sets a new passwordThe account now belongs to whoever clicked first.

Picture a 90-person distribution company. Over the years its accounting tool, its parcel carrier account, its LinkedIn page and a domain registrar login were all set up with invoices@ or info@ as the sign-in or the recovery address. None of those services knows who reads invoices@. They trust the inbox, and the inbox trusts its reader list, which nobody at the company has looked at since the finance team was three people.

The domain guide recommends role addresses as recovery for registrar and DNS accounts, and the same idea comes up for the logins behind company social pages. That advice holds, with one condition. A role address is only as safe as its reader list. Moving recovery off a founder’s personal Gmail onto info@ trades one person you can name for a group you may not be able to.

Google groups add an archive. If a group address has conversation history turned on, Google’s group settings page says members can view posts in Google Groups at any time. Google’s admin documentation lists “all organization users” as the organisation-wide default for who can view group conversations, and owners can change it per group. If nobody changed it for invoices@, every reset email, welcome email and bank detail change that ever reached that group can be read by anyone in the company. Reset links expire. Account names, supplier details and the list of tools registered to the address stay in the archive.

Accounts that belong to nobody can drift outside the rules for people. MFA rollouts, sign-in policies and password changes are planned around people. Microsoft’s own January 2024 account of the Midnight Blizzard intrusion says the attackers got in through password spraying against a legacy, non-production test account that did not have MFA enabled. That was a test account. The lesson carries over to info@ run as a user: an account with no person attached can be the one a rollout skips. The Midnight Blizzard file has the rest.

the inbox nobody offboards

A leaver checklist removes the leaver’s own account. A role address can keep them inside in three ways.

The password they knew. With the shared-password pattern, a departing employee knows the info@ password, and disabling their own account does nothing to it. Changing it means telling everyone who stays, which is a reason to put it off. If MFA on info@ was registered to one person’s phone, that person stays the recovery path after their last day. The shared vaults guide explains why a credential someone has seen should be treated as known.

The permission nobody revisits. In a real shared mailbox, Full Access granted to a person stays until somebody removes it. Moving from finance to sales does not take invoices@ away, which is the stayers guide in one mailbox. Microsoft’s permissions page also notes that Full Access can be granted to a mail-enabled security group. Then the mailbox’s permission list shows the group, and the people who can actually read the mail are whoever is in that group today. Reviewing the mailbox means reviewing the group too.

The leaver’s own mailbox, turned into a shared one. Microsoft’s offboarding series offers, as one step, converting a former employee’s mailbox into a shared mailbox so a colleague can pick up their mail. The conversion page carries two warnings worth reading slowly. If you do not reset the password, the original username and password continue to work on the shared mailbox after conversion. And inbox rules are preserved. So a forwarding rule the person set up before leaving travels with the mailbox, and the mail layer guide explains why such rules are easy to miss. The conversion page itself sends admins to the former employee steps to make sure the person can no longer sign in. Convert, then block sign-in, then reset the password, then read the rules.

A role address has as many owners as it has readers. Is any of them on your leaver checklist?

what a clean setup looks like

The fix is to treat each role address as an account with members, using the controls the platform already has.

  • Personal logins only. In Microsoft 365, every role address is a shared mailbox with sign-in blocked. In Google Workspace, it is a group, a delegated account or an admin-created shared inbox. No role address has a password a person knows.
  • One named owner per address. The owner approves who is on the reader list and who can send as it. The ownership guide explains why that person probably already exists.
  • Role addresses on the leaver and mover checklists. When someone leaves or changes team, remove their Full Access, Send As and group membership on the same day.
  • A list of what each address controls. Every tool, portal and page that uses the address as login or recovery, written next to the address.
  • Narrow groups for recovery that matters. For the registrar, the bank portal and the cloud root account, a small group of named readers is better than an address the whole finance team opens.
  • Group view settings checked. For Google groups used as inboxes, set who can view conversations to the group’s members.

questions the list will raise

The first export can produce names nobody expected: a former office manager on info@, an agency still in a support group, a whole team that inherited invoices@ through a security group. Each one is a decision about who should be able to reset your accounting tool.

The subject search will produce the harder list. It shows which tools trust the address, and some of them will be tools nobody remembers buying. Those go to whoever runs the switch-off method at your company.

Which of your tools would change hands if someone on the invoices@ reader list pressed “forgot password” today?

read next in the peopleA17 the assistant still has the keys to the boss's inboxone click makes an assistant a delegate. behind it sit four or five separate grants to a leader's mail and calendar, none with an end date, and attackers know how to add one of their own.

sources

  1. Microsoft Learn: about shared mailboxes in Microsoft 365
  2. Microsoft Learn: create a shared mailbox
  3. Microsoft Learn: manage permissions for recipients in Exchange Online
  4. Microsoft Learn: convert a user mailbox to a shared mailbox
  5. Microsoft Learn: remove a former employee, overview
  6. Microsoft Learn: manage mailbox auditing
  7. Google Workspace Admin Help: let users delegate access to a Gmail account
  8. Google Workspace Admin Help: create a shared inbox
  9. Google Workspace Admin Help: set organization-wide policies for using groups
  10. Google Groups Help: create a group and choose group settings
  11. Google Workspace Learning Center: use a group as a collaborative inbox
  12. Microsoft Security Blog: Midnight Blizzard, guidance for responders on nation-state attack (25 January 2024)