Google Updates Secondary Calendar Lifecycle & Announces New API

Google is refining how organizations manage calendar data during employee transitions. Google Workspace provided an important update regarding secondary calendar ownership, pushing back deadlines for paid accounts and announcing a new tool for administrators to handle data more effectively.

The goal of these changes is improved data governance, ensuring that important calendars don't simply disappear when a user account is deleted, while also giving IT teams the programmatic power they need to manage the shift.

1. Extended Deadline for Paid Accounts

Originally, Google announced that orphan secondary calendars (those whose owners had left the organization) would be deleted starting in April. However, based on customer feedback, the timeline has been shifted:

• New Enforcement Date: The policy where secondary calendars are permanently deleted upon the deletion of the owner's account will now take effect on October 5, 2026, for all paid Google Workspace accounts.
• Personal Accounts: For users with personal Google accounts, the original deadline remains, and deletion of orphan calendars will begin on April 27, 2026.

2. Coming Soon: New Calendar Transfer API

To help large organizations manage thousands of calendars, Google is launching a new Calendar API endpoint by the end of June 2026.

• Programmatic Transfers: Developers will be able to programmatically transfer ownership of individual secondary calendars within the same domain.
• No Confirmation Required: Mirroring current Admin console capabilities, these transfers will not require confirmation from the receiving user, making bulk offboarding much smoother.
• Admin Requirement: Using this API will require the Calendar administrator privilege.

3. The End of Auto-Assignment

Until the new October deadline, Google will continue a temporary process that auto-assigns ownership of orphan calendars to any user who has "Make changes and manage sharing" access.

• Important: This safety net stops on October 5, 2026.
• Action Required: Admins must now proactively ensure that owners transfer relevant secondary calendars to colleagues before they leave, or use the Admin console/new API to execute the transfer.

4. Ownership Rules to Remember

• In-Domain Transfers: Secondary calendars must be owned by a user within the same organization. Ownership transfers are restricted to users in the same domain.
• External Sharing: While ownership must stay in-house, you can still share calendars with external users and give them high-level permissions (like "Make changes and manage sharing") if your organization's policy allows it.

When a team member leaves, their knowledge shouldn't leave with them, and neither should their calendars. With the new October deadline and an upcoming API, Google is giving admins the breathing room they need to secure their organization's schedule.