"Our executive's secretary handles incoming inquiries on their behalf, but whenever that secretary steps away from their PC, responses come to a complete halt." We once received this kind of consultation from a general affairs manager at a company with around thirty-odd employees. While executives are away on business trips or meeting guests, a secretary uses the Gmail "delegation" feature to open incoming emails and reply in place of the executive when necessary. As an operational practice, this is not unusual. However, the moment that secretary heads out for a meeting, delegated handling suddenly becomes impossible—because delegated mailboxes could not be opened from smartphones.
Many companies face this exact same challenge, regardless of their size. Then at the end of June 2026, a foundational premise changed: Gmail delegation became available in the Gmail mobile apps as well. While it may look like a minor specification change, for companies that rely on individual-dependent operations where "one specific person handles another person's emails on their behalf," it turns out to have a surprisingly significant impact.
What Mobile Delegation Actually Allows You to Do
In June 2026, Google announced on the Google Workspace Updates blog that it would support operations for delegated accounts in the iOS and Android Gmail apps. Previously, delegated actions such as reading, replying to, and composing emails in a delegated mailbox were essentially restricted to the desktop web version of Gmail. With this update, delegates can view, manage, compose, and send emails for the delegator directly from the mobile Gmail app on their smartphones.
Within the app, users can tap their profile picture to switch to a delegated account and check unread counts for delegated mailboxes right from the account menu. In the "All inboxes" view, users can also see their own emails alongside delegated emails together. Sent emails also include information letting recipients know who sent the message on behalf of the delegator, matching the behavior of the web version.
The rollout is gradual, scheduled for completion around July 8, 2026, for Android and around July 29 for iOS. It covers a broad range of tiers: all Google Workspace editions, Workspace Individual, and personal Google Accounts. Importantly, no dedicated admin controls were introduced for this mobile capability; delegations already configured in the web version simply carry over. Looked at from another angle, for companies that currently lack visibility into who has been granted delegation access to which mailboxes, those accounts can now be opened directly from smartphones as well.
What Delegation Permits and What It Does Not
Before discussing convenience, let us clarify the terminology. If operations expand while these concepts remain ambiguous, information management issues will inevitably become tangled later. Gmail offers several distinct mechanisms that are frequently confused.
| How it works | Permissions | Best-Suited Scenarios |
|---|---|---|
| Delegation (email delegation) | View, reply to, compose, and delete another person's emails. No password sharing required | Executive secretaries, joint management of inquiry inboxes |
| Send mail as (adding an alias/sender address) | Send using a different address directly from your own inbox | Individuals using multiple sender identities |
| Automatic forwarding | Duplicate incoming emails to another address | Simple passing along of content, backups |
Delegation is a mechanism that "grants access to another person's mailbox without sharing their password." A delegated user can read, send, and delete emails belonging to the delegator. On the other hand, they cannot change the delegator account's password, modify settings such as forwarding or POP/IMAP, or chat via Google Chat. In other words, it is designed so that "someone can read and write emails on your behalf, but they cannot hijack the account itself." This philosophy differs from automatic forwarding or traditional shared mailboxes. We also touch upon fundamental email practices based on this clear division in our guide on business techniques for mastering Gmail at work.
There are also limits on the number of delegates. While an account can theoretically have up to several dozen delegates configured, the number of users who can access it concurrently is practically constrained depending on operational conditions. For setups where a small secretarial team of a few people manages a single executive account, it falls well within a realistic and practical range.
Pitfalls to Avoid to Ensure It Does Not End with "It Just Got More Convenient"
Mobile support is undoubtedly welcome, but from the standpoint of making procurement decisions, this is where the real issue begins. Delegation is frequently described as "safe because passwords are not shared," but that is only half the picture.
First, if a delegate's account is compromised, third parties will also gain access to the delegator's emails. No matter how strictly the delegator secures their password and two-factor authentication, if the smartphone on the receiving end is vulnerable, it becomes an entry point. Being able to access delegated mailboxes from smartphones naturally increases the physical device risk of the delegate. Rules governing device usage—such as whether personal smartphones are permitted, mandatory screen locks and biometrics, and response protocols for lost devices—should be elevated a notch higher than when access was primarily web-based. We have compiled organizational inspection points in our Google Workspace security checklist.
Second is the handling of offboarding and reassignments. Once configured, delegation remains active until explicitly revoked. In organizations that do not perform periodic audits, scenarios where "a departed secretary still technically has active delegation access allowing them to open their former manager's emails" are surprisingly common. Separate from suspending the delegator's account, operations require a master inventory to confirm who currently holds active delegation access to whom, ensuring unneeded access is stripped. While handling departing employee accounts themselves is detailed in managing departing employees' Google Workspace accounts, delegation is an independent issue that cannot be solved simply by deleting accounts.
Third is the auditing perspective. Although emails sent via delegation record who sent them on the delegator's behalf, few companies can routinely track who viewed a delegated email and when. If multiple people handle sensitive messages addressed to executives, deciding who receives delegation access should be governed by clear standards rather than intuition.
Redesigning Individual-Dependent Email Operations as a Systematic Process
The pitfalls highlighted so far ultimately stem from an individual-dependent state where "a specific person's emails are handled by another specific person through goodwill and habit." While mobile support can prolong such operational habits, it also serves as an excellent opportunity to revisit system design.
For example, rather than relying on a single secretary to manage an executive's contact point, reorganizing it so that "a team manages a shared inquiry address via delegation" ensures operations continue even if one person leaves. Translating delegation assignments into role-based rules and establishing recurring audit routines—rather than manually adding and removing access on an ad-hoc basis whenever staff join or leave—is essential. This kind of structural design for email workflows cannot be achieved merely by knowing features; it requires mapping them to your organization's structure and operational workflows.
When we assist clients through our custom development and consulting services, we rarely jump straight into tool settings. We begin by auditing whose emails need to be handled by whom and under what circumstances, distinguishing whether delegation, sending as an alias, or a shared mailbox is appropriate. In the case of the general affairs manager mentioned at the beginning, shifting from single-secretary delegation to a two-person delegation setup combined with device rules ensured responses never stalled on the go, while offboarding removals became part of standard procedures. Mobile support allows such operational designs to function with far less friction.
Where to Start
The first step to take following this update is not rushing to adopt the new feature, but rather conducting a complete audit of currently active delegation settings across the company. Map out who currently holds delegation access to whom, and check whether any departing or reassigned staff are involved. Only after clarifying this landscape can you safely reap the benefits of mobile delegation.
If your company finds it challenging to establish audit criteria or overhaul personalized email workflows on its own, bringing in external expertise is a sensible step. While mundane, email routing serves as the core communication lifeline of any business. Please feel free to consult with us.
