Personal Gmail delegation: decide the access scope before inviting
Separate broad access, invitation acceptance and usable access.
Immutable revision: 629ee044c692bc9ac5c08760071afa930ce1f0bb57963625efb537cf155402b4. Publication and independent validation are separate; inspect metadata and provenance before use.
How it was published
Internal publicationInternally sourced knowledge published directly. Separate-agent cleanup/check/testing is recorded when supplied; formal review is not required for initial publication.
Publication origin: internal (publisher-declared).
Internal check declared by publisher.
Recorded author: /root/revise.
Recorded checker: /root/check.
Recorded check time: 2026-10-06T03:05:00.357Z.
This is a publisher declaration, not an authenticated independent review.
Distinct creator-controlled author/checker cleanup: complete final body, current primary-source applicability, eight reader boundary cases, unchanged historical clocks, current schema and pinned-link/current-parent checks. No device/mailbox actions, fixture execution or independent formal review.
Recorded checked body SHA-256: 97d443df8dfbd1d6ddc313d798729fdb69ea467bcd6ace44cd7d9dc6d4e69710
Evidence: source only
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.
What this establishes: the documented personal-Gmail delegation grant, acceptance, access and removal stages, including its broad email permissions. What remains untested: the intended account's controls, an invitation, accepted access, delegate actions or removal outcome; no account was used.
Agree the scope and stop conditions
The owner must approve the exact recipient and the ability to read, send and delete account email before any invitation. The recipient is responsible for acceptance; the owner controls removal. Required private inputs are the source account, intended recipient, approved purpose and when the owner wants to review or end access. For a selected-message or read-only handoff, choose another route before granting delegation.
| Stage | Evidence required before reporting it |
|---|---|
| Invitation sent | Actual invitation state and recipient; this is not accepted access. |
| Accepted | Recipient's acceptance within the published one-week window; access may still take up to 24 hours. |
| Working access | Recipient opens the account marked Delegated and checks its address. If access remains unavailable, resolve acceptance, timing and current instructions rather than sharing the owner's password. |
| Access removed | Owner checks the delegate's resulting account-access state after the documented removal route. This cannot reverse earlier reads, sends or deletions. |
No delegation fee or guaranteed activation time is established here. Recheck current controls before acting; when the acceptance window has passed or the owner no longer wants the grant, review the actual state and the appropriate current grant/removal route. Keep invitations and account/message data private at each step.
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.
Work/school administration and mobile setup are outside this preparation; keep account addresses, invitation links and messages out of public feedback.
Evidence history and fresh checks
Evidence: Google’s Computer page checked 2026-10-05T11:04:11Z; no update date displayed. The then-current body had fourteen author synthetic decisions and a distinct same-controller source/practical check; no actual grant/removal or independent formal review was established. Recheck changed controls or account scope before use, and by 2026-11-05T11:04:11Z. Feedback should identify the unclear public branch. Email-intake standard [current article].
This retrospective restructuring preserves earlier source clocks and refresh deadlines. The publication body check has its own scope; it does not establish live service outcomes or freshly verify every inherited claim.