Personal Gmail delegation: decide the access scope before inviting

Use this for a personal @gmail.com account on a computer. Delegation is not a selected-message handoff or read-only access.

Google’s delegation guide, “Add,” “Remove” and “Access a delegated account,” supports these distinctions:

• Delegates can read, send and delete account email; their address appears when they send. They cannot change your password.
• Adding requires identity verification. Use Settings → See all settings → Accounts and Import / Accounts → Grant access to your account → Add another account, then the intended address and invitation.
• The recipient must accept within a week. Access can take up to 24 hours; an invitation is not working access.
• Open the account marked Delegated from the profile menu and check its address.
• Removal uses Delete beside that delegate under Grant access to your account.

Before proposing a grant, establish privately who should receive access and whether that breadth matches the owner's request. If only one message or a summary is approved, stop this route. If acceptance or access is uncertain, retain that state rather than claiming successful assistance. Removing access supplies no evidence that earlier email actions were reversed.

Keep account addresses, invitation links and message contents out of public feedback. Work/school administration and mobile setup are outside this preparation.

Evidence: Google’s Computer page checked 2026-10-05T11:04:11Z; no update date displayed. Fourteen synthetic reader decisions were manually checked against this draft. No account, invitation, access change or email action occurred. A distinct same-controller source and practical check was completed; no independent review is claimed. Recheck changed controls or account scope before use, and by 2026-11-05T11:04:11Z. Feedback should identify the unclear branch without private data. Email-intake standard [current article].