in this guide
  1. what “make them a delegate” switches on
  2. why it outlives the assistant’s job
  3. how attackers use delegation
  4. what the logs can tell you
  5. a short register for a small number of mailboxes

A new executive assistant starts on a Monday. By lunchtime someone has opened the managing director’s mailbox settings and made the assistant a delegate, because the assistant cannot do the job without it: answering mail, accepting meetings, moving the diary around. Google’s own admin help uses exactly this case as its example of delegation.

That one step is several grants at once. Read access to every message, the right to send mail that may or may not show who really wrote it, every meeting invitation routed through the assistant, sometimes the private appointments too. None of them has an end date, and none of them is attached to the assistant’s job title. They are attached to two accounts, and they stay until somebody removes them.

This guide is about that bundle. It pairs with the mail layer guide, which shows how hard it is to list delegations in Google Workspace, and with the stayers guide, which describes the general pattern of access that outlives the role it was granted for. Here the access in question is a leader’s inbox, and the record below shows attackers going after exactly that.

what “make them a delegate” switches on

The word delegate covers different grants in each product, and the screens do not always show them side by side.

In Microsoft 365, mail. Exchange Online has three mailbox permissions, and Microsoft’s documentation calls anyone holding them a delegate. Full Access lets the delegate open the mailbox and view, add and remove its contents, though not send from it. Send As lets the delegate send mail that appears to come from the mailbox, and Microsoft’s description is plain: “There’s no indication that the message was sent by the delegate.” Send on Behalf puts both names in the From line. If a user holds both sending rights, Send As wins.

In Microsoft 365, calendar. Outlook’s delegate access is a separate grant on the calendar folder. A delegate with the Editor level can create, change and delete items, including ones the owner created, and can accept or decline meetings on the owner’s behalf. Making someone a calendar delegate also creates a meeting message rule, so invitations and responses are delivered to the delegate. Whether the owner still gets a copy is a choice made at setup. A separate option lets the delegate see items marked private.

In Google Workspace, mail. A Gmail delegate can read, send and delete mail in the owner’s account. Google’s help says a delegate cannot use chat or change the owner’s password. Whether the recipient sees the delegate’s address alongside the owner’s, or only the owner’s, is a setting the admin picks for the organisation and can let users change.

In Google Workspace, calendar. Calendar sharing is its own set of levels. The top level, “make changes and manage sharing”, gives full control of events and the right to share the calendar with others. An assistant with that level can pass the leader’s diary on to someone else without the leader doing anything.

what one delegation can open on a leader's account

  • read every messageFull Access, or a Gmail delegate
  • send as the leaderSend As leaves no trace for the recipient
  • send on behalfboth names show
  • run the diaryaccept, decline, create meetings
  • see private itemsan extra tick box in Outlook
  • share the diary onwardGoogle's top calendar level

the grants that are easy to give without noticing

Both vendors keep this inside the organisation. Microsoft says you cannot give editor or delegate access to people outside your organisation, and Google limits mail delegation to users in the same organisation. So every delegate is a colleague, and a trusted colleague’s access is easy to leave alone.

why it outlives the assistant’s job

Nothing in either product connects a delegation to a role. Microsoft’s pages describe how to add and remove delegates, and removal is a manual step by the owner or an admin. Google’s are the same. So every ordinary change in an assistant’s working life leaves the grant behind.

Picture a 140-person company. The office manager has supported the managing director for four years with Full Access and Send As. She moves into an operations role. A new assistant is set up with the same rights. Nobody removes the old ones, because the old ones are not broken and the office manager is still a trusted colleague. A year later the managing director leaves, the mailbox is kept for handover, and two people still have the keys to it, one of whom has not needed them for a year.

how one leader's inbox collects delegates

  1. 1assistant startsFull Access, Send As, calendar delegate. A good reason, written down nowhere.
  2. 2holiday coverA colleague gets the same rights for two weeks.
  3. 3assistant changes roleA new assistant is added. The old grants stay.
  4. 4leader leavesThe mailbox is kept for handover, with every delegate still on it.
  5. 5one delegate account is phishedThe attacker signs in as the delegate and opens the leader's mail.

A few details make the pile harder to see.

  • Groups as delegates. Microsoft’s own example adds a group called tempassistants to the Send on Behalf list of an executives mailbox, and Google lets admins allow a group to be a mail delegate. From then on the real list of delegates is the group’s membership, which nobody looks at on the mailbox screen. The reorg guide explains why group membership tends to grow and rarely shrinks.
  • Switching delegation off is a pause. Google’s admin help says that when you turn off mail delegation, existing relationships in the organisation are turned off but not deleted, and they become active again immediately if delegation is turned back on.
  • The owner’s password does not end it. Google’s Gmail help notes that a delegate can still reach the account even after the owner’s password has expired. To stop the delegate, you reset the password or remove the delegate.
  • Cover during leave. When a leader is away for months, delegation is the usual way to keep work moving. The leave of absence guide covers that case, and the same question applies when they come back.
  • The leader’s own departure. Microsoft’s own leaver steps offer converting the mailbox to a shared mailbox for handover, and the shared mailbox guide covers what that conversion carries over.

A delegation is granted to a person and outlives the job they were given it for.

how attackers use delegation

There are two ways delegation shows up in the attack record, and they point the same way.

Delegation as a way to stay in. In June 2011 Google described a campaign that, in its words, appeared to originate from Jinan, China, and hit what seemed to be the personal Gmail accounts of hundreds of users, senior US government officials among them. Google said the goal seemed to be monitoring their mail, with the attackers apparently using stolen passwords to change forwarding and delegation settings. Its advice to users was to check for suspicious forwarding addresses and delegated accounts. That was espionage against personal accounts, but the mechanism is the one that matters to a business: once a delegate is added, the attacker reads the mail through a different account.

MITRE’s ATT&CK catalogue lists this as a technique of its own, additional email delegate permissions, used to keep persistent access. Its examples include Exchange’s Add-MailboxPermission and Google Workspace delegation, and it lists a group it tracks as Magic Hound as having granted compromised accounts read access to the mailboxes of other targeted accounts. ATT&CK’s first listed mitigation is short: if email delegation is not required, disable it.

CISA’s eviction guidance includes the same check. When responding to an incident involving business email compromise, it says, administrators should audit mailbox access logs and confirm that additional email permissions were not delegated, and it names the Exchange commands that list mailbox and folder permissions for that check.

The reason it works is the mechanism above. A delegate signs in with their own account. Resetting the leader’s password, or revoking the leader’s sessions, changes nothing for the delegate.

The leader’s mailbox as the target. In January 2024 Microsoft said an attacker it calls Midnight Blizzard had accessed a very small percentage of its corporate email accounts, including members of the senior leadership team, and taken some emails and attachments. Microsoft’s guidance for responders says the attacker used a legacy test OAuth application to grant an Exchange Online role that allows access to mailboxes, so no human delegate was involved; the Midnight Blizzard record tells that story. The point it adds here is about the target. Leadership mail is where the approvals, the board papers and the payment instructions sit.

An assistant’s account with Full Access is a second door to that mail, and it can get less attention than the leader’s own login. No public source counts how often attackers come in that way, so this guide makes no claim about frequency. The door exists whenever the grant does.

what the logs can tell you

Microsoft logs delegates by default. Its mailbox auditing documentation says auditing is on by default for user and shared mailboxes, and it records actions under a Delegate sign-in type for anyone holding Full Access, Send As or Send on Behalf. Sending as or on behalf of the owner, accessing mail items, changing inbox rules, changing folder permissions and deleting messages are logged for delegates by default. When the owner assigns a calendar delegate, that is logged too. Admins can set a per-user bypass that stops logging for a named account, so check that none exists for anyone holding delegate rights.

Google is thinner. The admin console decides whether delegation is allowed, and which sender information recipients see. It does not list who has delegated to whom. Google points admins to the Gmail API for that, and the mail layer guide walks through the price of doing it.

Calendar is a separate object in both products. In Microsoft 365 the calendar delegates sit in the calendar folder’s permissions, which PowerShell lists with Get-MailboxFolderPermission. In Google Calendar they sit in the “shared with” list in that calendar’s settings.

a short register for a small number of mailboxes

In a small company the accounts worth this attention are few: the leaders, finance, and whoever can approve money. Keep a register of delegations for those accounts only, and give each row four fields.

  1. Who holds it, and which grants. Full Access, Send As, Send on Behalf, calendar delegate, private items, Google calendar sharing level.
  2. Why. One sentence a third person could check.
  3. What ends it. A date, or a named event such as the assistant’s role change or the end of holiday cover.
  4. Who removes it. A named person, ideally whoever runs the joiner, mover and leaver process.

Two defaults reduce the damage when a grant is forgotten. Prefer Send on Behalf over Send As, so recipients can see who wrote a message. Leave the private items option off unless the leader asks for it. And for anything involving money, the check in the payment approval guide still applies, because a mail sent from a leader’s mailbox proves only that someone with access to it sent it.

The last time an assistant at your company changed jobs, who removed their access to the leader’s mail, and where would you look to find out?

read next in the peopleA18 the access you granted in a chat messagesomeone asks in a direct message, an admin clicks add, and the grant is done. the log keeps the click. the reason, the approval and the end date stay in a chat that expires first.

sources

  1. Microsoft Learn: manage permissions for recipients in Exchange Online
  2. Microsoft Support: manage another person's mail and calendar items
  3. Microsoft Support: share and access a calendar with edit or delegate permissions in Outlook
  4. Microsoft Learn: Add-MailboxFolderPermission
  5. Microsoft Learn: manage mailbox auditing
  6. Microsoft Learn: remove a former employee, overview
  7. Gmail Help: delegate and collaborate on email
  8. Google Workspace Admin Help: let users delegate access to a Gmail account
  9. Google Calendar Help: share your calendar with someone
  10. Official Google Blog: ensuring your information is safe online (1 June 2011)
  11. MITRE ATT&CK: T1098.002, account manipulation: additional email delegate permissions
  12. CISA eviction strategies tool: audit and restrict mailbox permissions (CM0074)
  13. MSRC: Microsoft actions following attack by nation state actor Midnight Blizzard (19 January 2024)
  14. Microsoft Threat Intelligence: Midnight Blizzard, guidance for responders on nation-state attack (25 January 2024)