2026 Gmail Mobile: Delegated Mailboxes by Role and Alias

A delegated Gmail mailbox is visible on mobile, but the owner must grant access in Gmail on the web first.

Fastest route: set up delegation in the web settings, then switch to the delegated mailbox in the Gmail app. Use delegation when someone needs to work in an existing inbox; use an alias or forwarding when the goal is to route mail to a different address.

For assistants and collaborators handling someone else’s Gmail from a phone.
For small-team leads deciding who can access a shared work inbox.
For freelancers and long-term email users separating client, project, and personal addresses.

Last updated October 23, 2026. Google’s official Workspace update and Gmail help pages were checked for mobile support, setup, and delegation limits.

Mailbox owners: access permission, not a new address

Gmail delegation gives another person permission to access an existing mailbox. Google’s help documentation describes delegate actions that include reading, sending, and deleting messages. This is not the creation of another Gmail address, and it does not give the delegate a separate inbox with an independent message history. Google’s Gmail delegation guidance explains the permission model and web setup.

That distinction matters before granting access. Delegation is suitable when a person must take action inside a mailbox that already receives mail—for example, an assistant processing scheduling requests from an owner’s inbox. It is not a routing rule, a backup copy, or an address-management system.

Does Gmail delegation need to be set up on a computer first?
The owner needs to configure delegation in Gmail’s web settings. The mobile app is for accessing a mailbox that has already been delegated; it does not replace the owner’s web setup. The official mobile announcement, published in June 2026, describes working with delegated Gmail accounts from mobile devices and identifies both Android and iOS app access. Google’s mobile delegation announcement is the source for that support. Availability can still depend on the account, app, and organization settings.

Before adding a delegate, the owner should define the work rather than grant access by habit:

Decide which messages the delegate should handle and which should remain owner-only.
Agree on whether the delegate may reply, delete, label, or archive messages.
Choose a way to review actions, such as checking sent messages and unresolved threads.
Set a point for reviewing or removing access if the role changes.

The permission is attached to a mailbox, not to one project label or folder. If a delegate can access the mailbox, the owner should not assume that labels alone create a security boundary. Use a separate address or account when work must be isolated from the owner’s other mail.

Google’s documentation also distinguishes delegation from sending as an alias. An alias can be an alternate sending or receiving address, but it does not itself grant someone access to the Google account or mailbox. For practical long-term address planning, compare that role boundary with the options described in our guide to email aliases and forwarding.

Delegates: mobile switching and sender checks

After the owner grants access, the delegate can open the Gmail app and use the account menu to switch to the delegated mailbox, where the account is available. Switching is important: seeing a message in a general view does not always mean the delegate is currently operating in the right mailbox identity.

A safe mobile routine separates triage from action:

Open the account menu and select the delegated mailbox before replying or deleting.
Check the mailbox identity at the top of the screen after switching.
Review unread indicators in that mailbox, not only the combined view.
Use “All inboxes” for a broad scan only when the relevant accounts appear there; switch into the delegated mailbox before taking an action that depends on its identity.
Before sending, inspect the From field and recipient details. After sending, check the sent message to confirm which mailbox sent it.

The Gmail app’s “All inboxes” view can help with scanning several available inboxes, but it is not a substitute for confirming the active account. A delegate who replies from the wrong account can expose a personal address, confuse a client, or leave a message outside the owner’s expected sent-mail record. The cost is not just an awkward correction: it can create ambiguity about who made a commitment.

Can recipients see who sent a message from a delegated mailbox?
Do not assume the message will look exactly like one sent by the owner alone. Gmail’s delegation guidance explains that messages sent by a delegate can identify the delegate’s action alongside the account owner’s address; the precise presentation can depend on the sending context. Check the From field and the sent copy before relying on a particular display. For sensitive client communication, send a test to an address the owner controls and confirm what the recipient sees. Google’s explanation of delegate access is the relevant official reference.

A delegate should also avoid treating “All inboxes” as a work queue with a guaranteed permission boundary. It is a convenience for viewing mail. For any reply, deletion, or decision with consequences, return to the mailbox that owns the conversation and verify the active identity.

Administrators: organization policy before mobile use

For a work account, the app experience follows the delegation already allowed for that account. There is no separate mobile permission that an administrator can enable to bypass organization policy. Before troubleshooting a delegate’s phone, confirm that the organization permits delegation for the account type and that its rules allow the intended relationship.

Google Workspace administrators should check the official policy and account-scope documentation rather than infer support from a working personal account. The Google Workspace administrator guidance on Gmail delegation covers administrative controls and restrictions. Google’s user-facing explanation of delegated account access provides another official reference for how the feature is presented.

For administrators, the main operational risk is granting a permission that outlives the work. Keep a record of the mailbox owner, delegate, business reason, and review point. When someone changes teams or leaves a project, remove access that is no longer required. A mobile app update does not change that responsibility.

Do not promise that every account will show the same menus or behave identically. The June 2026 announcement established mobile support, and Google posted a further restoration update on August 21, 2026. Those dated announcements confirm the product direction, not universal availability in every organization or configuration. The August 2026 update should be read alongside the account’s actual app and Workspace policy.

Freelancers and collaborators: match the tool to the job

A freelancer may need a client’s existing inbox handled by a collaborator, while also wanting separate addresses for project registrations, invoices, or newsletters. Those are different jobs. Delegation is about who can access and act inside a mailbox. An alias is about another address associated with an account or mail flow. Forwarding routes incoming messages from one address or mailbox to another destination.

Is Gmail mailbox delegation the same as a Gmail email alias?
No. A delegate is a person who receives permission to work in an existing mailbox. An alias is an address arrangement; by itself, it does not let another person sign in to or manage the mailbox. Forwarding moves messages to another destination, but it does not grant the recipient the owner’s full mailbox permissions. Keep “who can access the inbox?” separate from “which address receives the message?”

Use the following decision sequence:

If another person must read and reply to messages already arriving in a specific inbox, assess delegation.
If several people need to work from a shared team address under coordinated access rules, assess an organization-managed shared-mail workflow rather than relying on an individual’s personal mailbox.
If different websites or projects need distinct long-term addresses that all reach one destination, assess aliases or forwarding.
If an address should be independently stoppable when a project ends, make sure the chosen alias or routing setup supports that lifecycle.
If the need is a one-time sign-up or a single verification message, consider a temporary address instead of creating a permanent project identity.
If the account is important for banking, payments, government services, or long-term recovery, keep a durable address and recovery route under the account owner’s control.

For a customer-facing project, put the responsibility in writing. Record who owns the primary mailbox, who is authorized to reply, which address the customer should use, and what happens when the project ends. A short ownership record prevents the common failure where a collaborator retains access after the work has moved on—or where everyone assumes someone else is monitoring the address.

A role-based review before mobile work

Use this checklist before a delegate starts handling live messages:

[ ] The owner has granted access in Gmail on the web.
[ ] The organization permits delegation for this account and this relationship.
[ ] The delegate knows which mailbox to select in the Gmail app.
[ ] The owner and delegate agree on which messages may be answered, deleted, or left for review.
[ ] The delegate checks the active mailbox identity before sending.
[ ] The owner has reviewed a test message or sent copy to confirm how the sender is displayed.
[ ] The team has named an owner for unresolved messages and a date or event for reviewing access.
[ ] Any address intended for a different project or website has been evaluated separately from mailbox permissions.

This is not merely an onboarding list. It tests the points where the tools are easy to confuse: access versus routing, personal identity versus project address, and a temporary collaboration versus an ongoing responsibility. If the checklist fails on ownership or sender identity, pause live replies until the parties agree on the intended workflow.

Tool comparison: permission versus address routing

Need	Gmail delegation	Alias	Forwarding
Another person must work in an existing inbox	Fits when the owner grants access and policy allows it	Does not grant inbox access	Does not grant inbox access
A separate address for a client or project	Not its primary purpose	Can provide an alternate address, depending on account setup	Can route mail sent to another address
The recipient needs to send replies	Delegate can send from the delegated mailbox, subject to the sender context	Sending may require the alias to be configured for that purpose	Forwarding alone does not establish who may send as the original address
Access should end when a person’s role ends	Review and remove the delegate’s access	Disable or retire the address arrangement, if supported	Change or remove the routing rule
Best control question	Who may act inside this mailbox?	Which address should be used?	Where should incoming messages go?

The table describes different control layers, not interchangeable product features. In particular, forwarding is not a second copy guaranteed to serve as a backup, and delegation should not be used as a substitute for a durable address plan.

Address planning for long-term users

When a project needs a persistent address but not shared access to a personal inbox, keep the address layer separate from the permission layer. Maintain a simple record of each address, its purpose, its destination, and the person responsible for reviewing it. That makes later changes—such as ending a client relationship or replacing a receiving inbox—less dependent on memory.

Situation	Choose first	Review before committing
Assistant processes the owner’s current mail	Delegation	Scope, organization policy, sender display, and access removal
Several projects need separate inbound identities	Alias or forwarding	Whether replies are supported and how each address can be retired
A short-lived service registration needs an inbox	Temporary email	Whether the address remains available long enough for any follow-up
Long-term account recovery matters	Durable owner-controlled address	Recovery access, account ownership, and continued monitoring

These choices are not a ranking of products. They are a way to avoid using a permission feature to solve an address problem, or using a forwarding rule to solve a collaboration problem. For broader privacy and address-separation decisions, our email privacy guidance can help distinguish one-off sign-ups from accounts that need lasting access.

Mobile verification and access review

Before the delegate handles real correspondence, both parties should confirm that the workflow works in practice. The delegate switches into the mailbox, checks unread messages, sends an agreed test, and verifies the sent copy. The owner checks that the message was handled as expected and that the delegate did not reply from a personal address by mistake.

Repeat the review when responsibilities change. Remove a delegate who no longer needs access, and confirm that any active forwarding or alias arrangement still points to the intended destination. Delegation is access to a mailbox; it is not a backup mechanism and does not automatically create a second, independently retained copy of every message.

For an address that needs to remain separate from a main inbox, first decide whether the requirement is a long-term alias, forwarding, or just temporary receipt. If the need is only a short-lived registration or verification, Tempcat may be worth considering as an address-separation option; check the current service details before relying on it for retention, replies, or account recovery. It does not provide Gmail account delegation. Use delegation for a person who must work in an existing inbox, and use an address-layer option when the goal is to keep project mail separate from the primary address.