Gemini coworker accounts need a Workspace custody record

Name Workspace custody before creating the account

Open a custody record with the persistent account's immutable identifier, visible nonhuman display name, business role, sponsoring executive, service owner, Workspace administrator, records owner, organization, start date, expected end or review date, and approved continuity path. State whether the account is a lasting service role or a time-bounded team assignment. Do not use a departing employee's account, a shared human login, or an informal alias to represent the coworker; those shortcuts make ownership of its mail, events, and files impossible to reconstruct.

Assign a named custodian for the mailbox, calendar, My Drive content, shared-drive contributions, directory entry, and open work before the first message, invitation, or document is created. Record the applicable retention schedule and any legal-hold or records requirement for each object class. The custody record should say who can decide to transfer, retain, archive, cancel, or delete an item when the sponsor, team, role, or service ends.

Separate mailbox, calendar, Drive, and work ownership

A single account status does not settle the disposition of everything the account owns. For email, identify monitored threads, distribution or group relationships, delegated responses, drafts, and the address that should receive replies after a move or closure. For calendar, identify accepted invitations, recurring meetings, events the account organized, reserved resources, and external guests who may need a cancellation or a replacement organizer. State who may communicate the change and which sender identity should appear.

For Drive, distinguish files in the account's My Drive from content already governed by a shared drive. Record owned files and folders, externally shared links, pending access requests, comments, assigned document tasks, and documents whose workflow depends on the account. Decide which content transfers to a human or service owner, which remains in an approved repository, which is retained without active use, and which can be deleted after the applicable hold and retention checks.

Treat a mover event as a custody change

When the coworker changes sponsor, team, organization, business role, or duration, freeze the effective date and compare the old and new custody record. Inventory the mailbox threads, future and recurring calendar events, owned Drive items, shared-drive assignments, comments, drafts, and open requests that arose under the former role. For each class, record whether ownership stays, moves, is divided, is archived, or closes and name the receiving custodian.

Do not treat a renamed directory entry or a new sponsor field as proof that the move is complete. Confirm that future replies reach a monitored destination, recurring events have a valid organizer or are cancelled, Drive ownership reflects the approved destination, and unfinished work appears in the receiving queue. Keep the former and new effective states so a later records request can show which role owned an item at the relevant time.

Close pending work before the leaver event

Set a cutoff for new inbound work and identify every unfinished Workspace commitment: unanswered mail, scheduled sends, drafts awaiting review, accepted invitations, future and recurring events, open document tasks, unresolved comments, pending share requests, incomplete files, and handoffs promised in a thread. Assign each item to a named person or continuing service, cancel it with notice, preserve it under a retention decision, or record why no further action is required. A suspended account does not show that its commitments were resolved.

Sequence the leaver process around custody. Preserve the required snapshot, transfer approved mailbox and Drive records, change or cancel calendar ownership, publish the replacement contact where needed, close pending work, and then suspend or delete the account under the approved schedule. Test representative readbacks: reply to an existing thread, inspect a future invitation, open a transferred file from its destination, and confirm that the closure did not strand an external guest, collaborator, or records owner.

Issue a Workspace closure receipt

The final receipt should identify the account, role, sponsor, triggering joiner, mover, or leaver event, effective time, mailbox disposition, calendar disposition, Drive disposition, pending-work counts and owners, records and hold decisions, communications sent, exceptions, completed readbacks, and the administrators and business owners who accepted closure. Preserve unresolved items with an owner and due date rather than marking the lifecycle complete because the directory says inactive.

Review the custody record when Google changes account behavior, ownership-transfer functions, mail handling, calendar organizer rules, Drive storage, directory treatment, retention, or deletion behavior and whenever the organization changes the coworker's role or continuity plan. Google's announcement establishes current provider positioning for a dedicated persistent Workspace account. Only buyer records and readbacks establish who owns its work and whether a move or closure actually completed.

Turn this source into a reviewable decision

For AI for CIOs, use this briefing as a dated decision record rather than a substitute for the source. Preserve Google Cloud: Welcome to Gemini at Work 2026, the exact URL, the October 9, 2026 review date, the supported facts above, the editorial interpretation, the limitations, and any buyer-specific evidence. Link that record to the decisions most directly affected: Identity and agent access; Enterprise knowledge retrieval; Service management and employee support; Operations and incident intelligence. State whether the source changes the scope, evidence requirement, control, sequence, or only the language used to describe the decision.

Before action, name the accountable owner, affected population and workflow, exact offering or configuration, source data and rights, human decision point, exception and appeal path, complete cost, expected benefit, failure and stop conditions, retained evidence, and next review date. Keep official facts, provider statements, buyer observations, representative tests, measured outcomes, editorial inferences, and unknowns visibly separate. Reopen the record when the source, offer, model, integration, data, policy, population, responsible person, or measured result changes.

Limitations and unknowns

Google Cloud is the provider source. Its October 8, 2026 announcement describes persistent coworker agents, dedicated Workspace accounts, email, calendar, Drive, directory presence, and participation through ordinary Workspace surfaces. It does not establish a buyer's edition, entitlement, provisioning process, account configuration, mailbox routing, calendar ownership behavior, Drive location or transfer result, records and legal-hold requirements, pending-work inventory, sponsor or custodian decisions, suspension or deletion behavior, or closure outcome. Current contracts and Workspace documentation, account and ownership inventories, mailbox, calendar, Drive, directory, retention, hold, transfer, deletion, pending-work, and readback records, and qualified Workspace administration, records, legal, privacy, security, operations, business-continuity, accessibility, and procurement review control.