Workspace Secondary Calendars Now Die With Their Owner

An HR team deletes the account of someone who left two months ago. Routine. Except that person had created the shared meeting-room calendar, the one the whole team checks every morning. Before, that calendar would have stayed in place, ownerless but working. Since October 5, 2026, it leaves with the account. That is the direct consequence of a change Google now applies to non-personal Workspace accounts: a secondary calendar follows the lifecycle of its owner.

What actually changes

Until now, two different rules governed a user’s primary calendar and their secondary calendars. The primary calendar disappeared with the account, like the Gmail mailbox. Secondary calendars survived the owner’s deletion and stayed accessible to the people they had been shared with, in a state with no valid owner.

Google aligns the two behaviors. When an account is deleted, its secondary calendars and the events they contain are deleted with it. When an account is suspended, its secondary calendars are suspended at the same time. The stated rationale is governance: every calendar must be tied to a valid owner that determines the settings and policies applied to the data. A calendar with no active owner falls outside that framework, and that is exactly what Google removes.

The rollout started on October 5, 2026 for non-personal Workspace accounts, as an extended rollout on Rapid Release and Scheduled Release domains. The change applies to all Google Workspace customers and to Workspace Individual subscribers. No edition is spared, and there is no setting to turn it off. The announcement sits on the Google Workspace Updates blog of October 5, 2026.

The real risk: shared team calendars

The feature presents itself as a governance gain, and in principle that is correct. A calendar tied to an identified owner is easier to audit than a floating one. But the operational risk does not come from personal secondary calendars, which vanish with their creator without bothering anyone. It comes from the shared calendars whole teams use without knowing who owns them.

A room-booking calendar, a time-off planner, an editorial schedule, a project calendar: these are often created by one person, then shared widely. Over the months, no one remembers that the calendar technically belongs to a single account. Google’s help documentation states that deletion includes group calendars and Classroom calendars. The day that account is deleted during a departure, the calendar leaves with it, and so does the event history.

This is the point we would watch first. The change is sound in principle, but it turns an old oversight, a poorly attached calendar, into real data loss at offboarding time. The good news is that the problem is entirely avoidable if you know where to look.

How to keep a calendar before a departure

The safeguard is ownership transfer. To preserve a secondary calendar, you transfer its ownership to another active account before the original owner is deleted or suspended. An admin does this in the Admin console or through the Calendar API. A user can transfer their own calendars from Google Calendar settings.

One timing constraint matters here: the calendar must be active at the moment of transfer. A disabled or deleted calendar can no longer be transferred, and once the owner is deleted, no transfer is possible at all. In other words, the transfer must precede the account deletion, not follow it. An offboarding flow that deletes the account first and asks about calendars afterward arrives too late.

The reflex to adopt is to pick a durable transfer target. Moving a leaver’s calendar to another employee’s account only defers the problem to the next departure. For structural calendars, a functional mailbox or a service account, one that does not follow staff movements, is a better anchor. It is the same logic of durable attachment we recommend for sensitive roles in our article on temporary admin roles.

What this change does not solve

Tying every calendar to a valid owner improves traceability, but it is not a backup. A calendar transferred at the right time is preserved; a calendar forgotten in an account deletion is lost, events included, with no obvious recovery bin. The rule protects against orphaned calendars, not against human error during a departure.

For organizations whose work depends on shared schedules, that potential loss justifies a backup strategy covering Google Calendar alongside Gmail and Drive, as we lay out in our guide on backing up Google Workspace. Google’s change does nothing about this: it is a governance guardrail, not a safety net.

It is also worth noting that the feature does not act retroactively on your existing setup for you. It will not tell you which shared calendars are tied to accounts at risk of departure. That inventory remains an admin task, in the same spirit as the exposure audit we describe for API keys and Gemini.

What an admin should do now

The first action is a one-time inventory of critical shared calendars and their owners. For every calendar several people depend on, the question is simple: if this account were deleted tomorrow, would the organization lose something? If so, transfer ownership to a durable account before any departure.

The second action is to fold calendar transfer into the offboarding process, right next to Drive file transfer and event handling. A departure should trigger a check: does this person own shared secondary calendars? If so, transfer them before deleting the account. That reflex, written into the procedure, beats an after-the-fact audit, because once the account is deleted there is no recovery. To place this point within the broader set of settings to lock down, our guide to essential Admin console settings gives the general frame.

Read also

• Temporary Admin Roles in Google Workspace: What Changes: the same durable-attachment logic applied to sensitive rights.
• Google Workspace Backup: why and how to back up your cloud data: why native governance does not replace a real backup.
• Google Workspace: essential admin console settings: the settings to lock down from day one.

Are your team calendars tied to accounts that could leave tomorrow? We audit your shared calendars and fold their transfer into your offboarding process. Let’s spend 30 minutes on your setup.