For years there was one maddening gap in Google's assistant-and-executive workflow: you could hand someone the keys to your inbox on the desktop, but the moment either of you picked up a phone, the whole arrangement fell apart. That gap just closed. As of July 2026, Gmail delegate access finally works inside the Gmail app on Android, iPhone, and iPad — so an assistant can triage the boss's mail from a train platform, and a support lead can clear a shared queue without opening a laptop.
This is a bigger deal than a single feature note makes it sound. Millions of people run their day through delegated inboxes — executive assistants, help desks, family caretakers, small teams sharing a single "hello@" address — and until now every one of them was chained to a browser. If you have ever wanted to answer a delegated message from your couch, this guide is for you. Below we break down exactly what changed, how to set up Gmail delegate access the right way, what delegates can and cannot do on mobile, the security trade-offs, and how power users who run many inboxes should think about the update. Whether you manage one shared mailbox or a fleet of aged Gmail accounts, the mobile rollout changes your daily workflow.
What Gmail Delegate Access Actually Is
Gmail delegate access is Google's built-in way to let another person read, send, and manage email in your account without ever knowing your password. You grant a specific address permission to act on your behalf; they open your mailbox from inside their own Gmail, and every action is tied back to their identity. It is the sanctioned alternative to the thing far too many offices still do — sharing one password over chat and hoping for the best.
In Google's own terminology, a delegated account and a "shared inbox" are the same thing. When you delegate a mailbox, the person you add can open it alongside their personal mail, triage the queue, reply to customers, and archive what's handled. Crucially, when a delegate sends a message, the recipient can see that it was sent by the delegate on behalf of the owner — there is no impersonation and no hidden ghost-writing. That transparency is exactly why Gmail delegate access is the professional standard for assistants, support desks, and any team that shares a single point of contact.
What makes delegation different from simply logging into someone else's account is accountability and safety. The delegate never sees the owner's password, cannot change the account's security settings, cannot delete the account, and cannot manage the owner's other Google services. They get scoped access to mail and nothing more. For anyone who has ever winced at handing over full credentials, that scoping is the whole point.
What Changed in July 2026
The feature itself is old; the mobile support is brand new. For well over a decade, Gmail delegate access only functioned in the desktop web interface. You could grant it, and a delegate could use it — but exclusively from a computer. Open the Gmail app on a phone and the delegated mailbox simply did not exist. That single limitation quietly forced a generation of assistants and support agents to stay tethered to a desk.
In late June 2026, Google announced that the Gmail apps for Android and iOS would finally support delegated accounts, with the rollout completing by July 8, 2026 on Android and July 29, 2026 on iOS. The capability landed for everyone: all Google Workspace customers, Workspace Individual subscribers, and — importantly — ordinary personal @gmail.com accounts. This is not a locked-down enterprise-only perk. Here is what mobile Gmail delegate access now includes:
- Account switching. Tap your profile picture in the Gmail app and pick the delegated mailbox from the same list you use to switch between your own accounts.
- Full triage. Read, reply, forward, archive, label, and delete inside the delegated account, right from the phone.
- Unread counts. The account menu shows unread message counts for delegated inboxes, so a delegate knows a queue needs attention without opening it.
- All inboxes view. The mobile "All inboxes" view intermingles delegated mail with your own, giving one combined stream.
- Correct "sent by" attribution. Messages a delegate sends from the phone carry the same on-behalf-of information recipients already see from the web.
The best part: no admin configuration is required. Mobile Gmail delegate access simply honors whatever delegation you already set up on the web. If the desktop permission exists, the mobile app respects it automatically once the update reaches your device.
How to Set Up Gmail Delegate Access (Web)
Because you still cannot grant delegation from the phone, setup begins on a computer. The person who owns the mailbox performs these steps to add a delegate. It takes about two minutes:
- On a desktop browser, open Gmail and click the gear icon in the top right, then See all settings.
- Go to the Accounts and Import tab (labeled just Accounts on Workspace domains).
- Find the Grant access to your account section and click Add another account.
- Enter the email address of the person you want to delegate to and click Next Step, then Send email to grant access.
- Google may ask you to verify your identity to confirm you requested the change — complete that check.
- The delegate receives a confirmation email with a link. They must click it to accept. Acceptance can take up to 30 minutes to take effect, and sometimes a few hours to fully propagate.
Once the delegate accepts, Gmail delegate access is live everywhere — web and, now, mobile. You can choose whether delegates see the full email address of the sender in conversations or only the name, using the "conversation" vs "reference" setting in the same panel. Workspace administrators can also enable or disable delegation domain-wide from the Admin console, so if the "Add another account" option is missing on a work account, delegation may be turned off by your admin and you will need to ask them to allow it.
A quick note on security hygiene during setup: only delegate to addresses you trust completely, and audit the delegate list periodically. Because Gmail delegate access grants real control over your mail, treat it with the same care you would a house key. If you are hardening the account anyway, our guide to Gmail passkeys pairs well with delegation — passkeys protect the owner's login while delegation handles day-to-day access.
Using a Delegated Account in the Mobile App
Here is the workflow everyone has waited for. Once the July 2026 update reaches your device and the owner has granted you access on the web, opening a delegated mailbox on your phone is nearly identical to switching between your own accounts:
- Update the Gmail app to the latest version from the Play Store or App Store — mobile Gmail delegate access only appears once you are on the updated build.
- Open Gmail and tap your profile picture in the top-right corner.
- In the account list, the delegated mailbox appears beneath your own accounts. Tap it to switch.
- The delegated inbox loads. Read, reply, archive, and label exactly as you would in your own mail. Replies automatically carry the on-behalf-of attribution.
- To see everything at once, choose All inboxes — your mail and the delegated queue merge into a single chronological stream, with unread counts visible in the account menu.
The experience is deliberately familiar. If you have ever added a second personal account to the Gmail app, you already know the muscle memory. The one thing to remember is direction: the owner grants access from a desktop; the delegate consumes it on the phone. There is still no way to create a delegation relationship from a mobile device — only to use one that already exists. For assistants who were previously forced to carry a laptop just to cover the boss's inbox on the road, mobile Gmail delegate access removes that burden entirely.
What Delegates Can and Cannot Do
Delegation is powerful but intentionally scoped. Understanding the boundaries prevents nasty surprises. Here is the honest breakdown of what Gmail delegate access permits and forbids.
| Delegates CAN | Delegates CANNOT |
|---|---|
| Read incoming and archived email | Change the owner's password |
| Send and reply (with on-behalf-of attribution) | Change security or 2-Step Verification settings |
| Delete and archive messages | Chat or start Google Meet calls as the owner |
| Apply and manage labels | Add or remove other delegates |
| Search the delegated mailbox | Access the owner's Drive, Photos, or other services |
| Manage the shared queue on mobile | Delete the Google account itself |
The pattern is clear: Gmail delegate access covers email operations and stops precisely at the account's identity and security perimeter. A delegate is a highly capable mail assistant, not a co-owner. One frequent point of confusion is chat and Meet — delegation is mail-only, so a delegate cannot send chat messages or join video calls impersonating the owner. Another is the "sent by" line: because every delegated send shows who actually clicked the button, delegates cannot secretly pose as the owner, which is a feature, not a flaw. If your workflow requires truly anonymous shared sending, delegation is the wrong tool and a dedicated group or shared mailbox product fits better.
Delegate Limits, Personal vs Workspace
How many people you can delegate to depends on your account type, and the numbers are generous. Personal @gmail.com accounts can add up to 10 delegates. Work or school Google Workspace accounts can add up to 1,000 delegates — enough to run a large support organization from a single shared address. In every case the delegates must have Google accounts themselves, since Gmail delegate access ties each session to the delegate's own identity.
There are a few practical constraints worth knowing before you build a workflow around delegation:
- Same organization for some Workspace features. On managed domains, admins may restrict delegation to within the organization, so external delegates might be blocked by policy.
- Propagation delay. Newly granted Gmail delegate access can take up to a few hours to appear, and the same is true when it is revoked — don't panic if a change isn't instant.
- No nested delegation. A delegate cannot re-delegate the mailbox to a third person; only the owner controls the delegate list.
- Mobile requires the updated app. If a delegated account isn't showing on a phone, the device may simply not have received the July 2026 build yet.
For teams that need more than 10 shared users on a consumer address, the practical answer is either to move to Workspace or to distribute the load across multiple mailboxes. This is one reason operators who run outreach or support at scale keep a pool of well-established accounts rather than funneling everything through one — a strategy we cover in depth in how many Gmail accounts you need for sustained sending.
Security and Privacy Trade-Offs
Convenience always carries a cost, and mobile Gmail delegate access is no exception. Extending delegation to phones widens the surface where sensitive mail can be viewed. A lost, unlocked phone belonging to a delegate now potentially exposes the owner's inbox in a way it never did when delegation was desktop-only. That's not a reason to avoid the feature — it's a reason to use it deliberately.
Here are the guardrails that keep delegation safe now that it lives on mobile:
- Delegate only to people, not shared devices. Each delegate should use their own Google account on their own secured phone with a screen lock and biometric unlock enabled.
- Audit the delegate list quarterly. Open the Accounts settings on the web and remove anyone who no longer needs access. Stale Gmail delegate access is a classic overlooked risk.
- Revoke immediately on offboarding. When an assistant or agent leaves, pull their delegation the same day. Remember the propagation delay and verify it took effect.
- Protect the owner account first. Delegation is only as safe as the owner's login. Enable 2-Step Verification or passkeys so a compromised delegate can't cascade into a full account takeover.
- Watch for phishing aimed at delegates. Attackers know assistants handle valuable mail. The same social-engineering tricks in our roundup of 2026 Gmail scams target delegated inboxes too.
Used with these habits, Gmail delegate access is dramatically safer than the alternative it replaces — password sharing — because it never exposes credentials and it leaves a clean per-delegate trail. The mobile expansion doesn't change that calculus; it just means the same discipline now has to extend to every phone in the workflow.
Troubleshooting: When the Delegated Account Won't Appear
The most common complaint since the rollout is simple: "I set up delegation, but the mailbox isn't showing on my phone." Nearly every case traces to one of a handful of causes. Work through them in order.
- Update the app. Mobile Gmail delegate access requires the July 2026 build. Check the Play Store or App Store for a pending Gmail update and install it. On iOS the rollout completed later (by July 29), so iPhone users may need to wait slightly longer than Android users.
- Confirm the delegate accepted. Delegation isn't active until the delegate clicks the acceptance link in the invitation email. If that step was skipped, the mailbox never appears anywhere.
- Wait out propagation. A freshly granted delegation can take up to a few hours to surface on mobile. Give it time before assuming it's broken.
- Check the account list, not "Add account." The delegated mailbox appears automatically under your profile picture — you do not add it via "Add another account," which is only for accounts you own.
- Verify admin policy (Workspace). On managed domains, an administrator can disable delegation or restrict it to the organization. If a coworker's mailbox won't delegate, the admin console setting is the likely culprit.
- Force a sync. Pull to refresh, or sign out and back in on the app. A stalled sync can hide a delegated account that is otherwise correctly configured.
If none of that works and the delegation clearly exists on desktop, the issue is almost always the app version or a sync hiccup rather than the delegation itself. This mirrors a broader pattern in Gmail troubleshooting: the account is usually fine, and the client is the problem. If you're chasing missing messages rather than a missing mailbox, our companion guide on Gmail not receiving emails covers the six places mail hides.
Delegation vs Forwarding vs Shared Login
People reach for three different tools to solve "more than one person needs this inbox," and choosing the wrong one causes real pain. Here's how Gmail delegate access stacks up against the alternatives.
| Approach | Best for | Main drawback |
|---|---|---|
| Delegation | Assistants and teams managing one owner's mailbox | Owner must grant from desktop; no chat/Meet |
| Forwarding | Sending copies of mail to another address | No way to reply from the original address cleanly |
| Shared password login | Nothing — avoid it | No accountability, breaks 2FA, huge security risk |
Forwarding is fine when someone just needs to see copies, but it falls apart the moment they need to respond as the shared identity. Shared logins should be retired entirely — they defeat two-factor authentication, leave no audit trail, and trigger Google's suspicious-activity defenses when several people sign in from different locations. Gmail delegate access exists precisely to kill the shared-password habit: it delivers the collaboration teams actually want while preserving individual accountability. If your team is still passing one password around, migrating to delegation — now usable on every device — is the single biggest inbox-security upgrade you can make this year. Google is separately retiring older interop features too, as we covered in Gmail ending Gmailify and POP, so consolidating on native delegation is future-proof.
Managing Delegate Access Across Many Accounts
If you operate more than a handful of mailboxes — an agency running client inboxes, a support org, or anyone maintaining a pool of aged Gmail accounts — mobile delegation reshapes how you staff coverage. A few principles keep Gmail delegate access manageable at scale:
- Map delegates to roles, not people. Decide which mailbox each team member covers before granting access, so the delegate list stays legible and auditable.
- Standardize the acceptance step. The biggest bottleneck at scale is delegates forgetting to click the acceptance link. Build it into onboarding.
- Keep owner accounts hardened and warm. Delegation rides on the owner account's health; well-aged, properly secured accounts behave more predictably across the app's sync and switching.
- Document revocation. With up to 1,000 delegates possible on Workspace, an un-audited list becomes a liability fast. Track who has access to what.
- Test on both platforms. Android received the update first; confirm your iOS staff are on the July 29 build before assuming coverage is complete.
The strategic upshot is that delegation lets a small team cover a large number of inboxes without ever sharing a credential — and now without anyone being chained to a desk. For teams weighing whether to build that capacity in-house or source ready-to-run inventory, our comparison of buying versus creating Gmail accounts lays out the real cost and time math. Pairing well-established accounts with disciplined delegation is how professional operators run reliable, accountable inbox coverage in 2026.
Frequently Asked Questions
Can you now use Gmail delegate access on the mobile app?
Yes. As of July 2026, the Gmail apps for Android, iPhone, and iPad support delegated accounts. The rollout completed by July 8 on Android and July 29 on iOS, and it reached all Google Workspace customers, Workspace Individual subscribers, and personal @gmail.com accounts. You still grant delegation from a desktop browser, but once granted, delegates can open the mailbox by tapping their profile picture in the app and selecting the delegated account. Read, reply, archive, and label all work from the phone.
How do I set up Gmail delegate access?
The mailbox owner sets it up on a computer. Open Gmail settings, go to the Accounts and Import tab, find "Grant access to your account," click "Add another account," and enter the delegate's email address. Google may ask you to verify your identity. The delegate then receives an email and must click the acceptance link. After acceptance — which can take up to a few hours to propagate — the delegate can use the mailbox on both desktop and mobile. You cannot create the delegation from a phone; only use one that already exists.
Can a delegate see my password or change my security settings?
No. Gmail delegate access never exposes the owner's password and never grants control over security settings. A delegate can read, send, delete, and organize email, but they cannot change your password, alter 2-Step Verification, add or remove other delegates, delete your account, or access your Drive, Photos, or other Google services. When a delegate sends a message, recipients can see it was sent on your behalf, so there is no hidden impersonation. This scoped access is exactly why delegation is far safer than sharing a password.
How many delegates can I add to a Gmail account?
Personal @gmail.com accounts can add up to 10 delegates. Work or school accounts on Google Workspace can add up to 1,000 delegates, which is enough to run a large shared support queue from one address. Every delegate must have their own Google account, since each session is tied to the delegate's identity for accountability. On managed Workspace domains, an administrator can restrict delegation to within the organization or disable it entirely, so check with your admin if the option is missing.
Why isn't my delegated account showing up in the Gmail app?
The most common cause is an outdated app — mobile delegation requires the July 2026 Gmail build, and iOS received it slightly later than Android. Update the app first. Then confirm the delegate actually clicked the acceptance link, since delegation isn't active until accepted. Allow a few hours for a new grant to propagate. Remember that the delegated mailbox appears automatically under your profile picture, not through "Add another account." On work accounts, an admin policy may block delegation. A pull-to-refresh or sign-out and back in resolves most remaining sync issues.
Does a delegate's reply come from my address or theirs?
When a delegate replies from your mailbox, the message is sent from your address, but recipients can see attribution indicating it was sent by the delegate on your behalf. This transparency is built in and cannot be hidden — it's what separates Gmail delegate access from impersonation. The same on-behalf-of information now appears on messages sent from the mobile app, matching the long-standing desktop behavior. If your workflow requires fully anonymous shared sending with no attribution, a Google Group or dedicated shared-mailbox product is a better fit than delegation.
Mobile Gmail delegate access is a small feature note with a big daily impact: assistants, support teams, and anyone sharing an inbox can finally do the job from a phone, without passwords and without a laptop. Set it up once on desktop, secure every device that touches it, and audit the delegate list regularly. If you run inbox coverage at scale and want reliable, well-aged accounts that stay consistent across delegation, sync, and sending, message our team on Telegram at @mixgmail and we'll help you build a setup that fits your workflow.
