We recently
announced a change to the ownership model of secondary calendars to improve data governance. As part of this, we emailed impacted customers to let them know that orphan secondary calendars would be deleted starting on April 27, 2026.
Since that announcement, we’ve received valuable feedback that to properly manage this new lifecycle, customers need better programmatic tools to handle secondary calendar data before it gets deleted.
To ensure you have the time and tools necessary to manage this transition smoothly, we are making two important updates:
- We are launching a new API endpoint by the end of June to transfer secondary calendars within your organization.
- We are postponing the secondary calendar lifecycle changes to October 5, 2026 for non-personal Workspace accounts.
Coming soon: new API endpoint to transfer secondary calendars
In the coming months, we’ll introduce a new endpoint in the
Calendar API that will allow developers to programmatically transfer the ownership of secondary calendars. This endpoint will require the
Calendar administrator privilege.
The API will mirror the existing capabilities in the Admin console—transferring secondary calendars within the same organization without requiring confirmation by the receiving user—and introduces the additional flexibility to transfer individual calendars.
The new API endpoint will be available for integration by June 2026. An announcement and technical documentation will be published when the API goes live.
Extended deadline for lifecycle changes
To give your teams ample time to adjust their workflows and integrate with the new API endpoint, we are officially pushing back the enforcement date for the secondary calendar lifecycle changes for non-personal Workspace accounts.
The new policy—where secondary calendars are permanently deleted upon the deletion of the owner's account—will now take effect on October 5, 2026, for non-personal Workspace accounts.
Until then, we will run a regular process for orphan calendars that auto-assigns ownership to a user who has “Make changes and manage sharing” access. This process will stop on October 5, 2026. Instead, make sure to ask the owner to transfer relevant secondary calendars to a colleague before they leave - or make sure an administrator executes the transfer using the Admin console or the new API endpoint.
Note that the changes to the secondary calendar lifecycle will still take effect on April 27, 2026, for users with personal Google accounts.
Additional details
Secondary calendars owned by an organization must be owned by a user within that same organization, and ownership transfers are restricted to users in the same domain. However, you can continue to share calendars with users outside your organization—including with high-level permissions such as "Make changes and manage sharing"—provided your
organization policies allow it.
 |
| Example of a secondary calendar owned by the dwelling.com organization, with elsonl@dwelling.com as owner |
 |
Example of a personal secondary calendar (not owned by an organization), with amandahayes@gmail.com as owner |
Getting started
- Admins: Stay tuned for more details on the new API endpoint when it launches.
- End users: There is no end user setting for this feature. End users can already transfer secondary calendars to other users within their organization. Visit the Help Center to learn more.
Rollout pace
- Rapid Release and Scheduled Release domains
- New API endpoint: Gradual rollout (up to 15 days for feature visibility) starting in June (to be announced on Workspace Updates blog when available)
- Secondary calendar lifecycle change: Gradual rollout (up to 15 days for feature visibility) starting on October 5, 2026
- Users with personal Google accounts
- Secondary calendar lifecycle change: Gradual rollout (up to 15 days for feature visibility) starting on Apr 27, 2026
Impact
- All Google Workspace customers and users with personal Google accounts are impacted by these changes
Resources
