This article reviews Google Calendar updates announced from June through August 2026 and describes their status as of September 16, 2026. It is intended for Google Workspace administrators, executive assistants, and operations teams that manage shared calendars. The recommendations are an editorial operating framework, not the result of firsthand testing or an endorsement.
Quick answer
Ownership transfer for secondary calendars through the Calendar API became generally available on June 18, 2026. The process is limited to active secondary calendars transferred between users in the same organization, and it requires a Google Workspace administrator with the Manage Calendars privilege. Calendar API release notes Ownership-transfer reference
The Make changes (see private events as free/busy) permission allows changes to non-private events only. Private events marked Busy appear as busy blocks, while private events marked Free do not appear. A delegate with this permission cannot edit private events or find them in search. Google Calendar sharing permissions Google Workspace announcement
An organizer or delegate can suppress RSVP messages and automatic replies. Google Calendar users’ statuses remain visible, but the RSVP status of users on external tools such as Outlook is not shown when messages are suppressed. For recurring events, the setting applies to the entire series. Announcement on suppressing response messages
Calendar blocking applies to invitation organizers who use Google Accounts and prevents future invitations from them. For people who do not use Google, their email address must be blocked in Gmail. Other existing invitations may remain, so review and manually delete them when needed. The extended rollout was expected to finish on September 18, 2026, so the feature may not be visible to every account on September 16. Announcement on blocking invitation organizers Google Calendar blocking instructions
Review ownership before moving a calendar
The Calendar API provides a general path for transferring active secondary-calendar ownership, but it is not a general transfer path for every calendar type. The API reference says the transfer must be between users in the same organization and must be performed by a Google Workspace administrator with the Manage Calendars privilege. transferOwnership reference
The Calendar API release notes state that general availability began on June 18, 2026. They also describe an organization filter that helps limit the set to calendars owned by the organization. Calendar API release notes
Editorial recommendation: Keep an internal inventory showing each secondary calendar, its status, the owner’s organization, and the administrator authorized to perform a transfer. This is an operational recommendation, not a claim about an additional product capability.
Sharing and privacy
The Make changes (see private events as free/busy) permission is intended for cases where a delegate needs to edit non-private events without seeing private-event details. It allows changes to non-private events only. Private events marked Busy appear as busy blocks, while private events marked Free do not appear. The delegate cannot edit private events or find them in search. Google Calendar sharing help Google Workspace announcement
This article’s practical recommendation is to review delegate permissions against the minimum role needed, then test what each role can see using non-sensitive test events. That is a proposed validation step, not a reported test result.
Recurring events: do not assume a separate copy
A visibility change for a recurring event applies to the entire series and can no longer be applied to only one instance. If visibility differs within an existing series, the series is updated according to its strictest privacy setting. Announcement on recurring-event visibility
For that reason, this article does not recommend creating a new mixed series after the update. Use an existing series only after reviewing the effect of the change, or test with a test series first. The purpose of the test is to observe how the change appears to the actual roles in your organization, not to infer undocumented behavior.
RSVP and automatic replies
An organizer or delegate can stop receiving guest-response messages and automatic replies for the event. Google Calendar users’ statuses remain visible, but the RSVP status of users on external tools such as Outlook is not shown when messages are suppressed. For recurring events, the setting applies to the entire series. Announcement on suppressing response and update messages
Suggested operating design: Before using this setting for a series your team relies on, record who needs response visibility, then test one Google Calendar user and one external-tool user. This is a proposed check, not a guarantee that an existing workflow will remain unchanged.
Blocking unwanted invitations
The blocking feature covers Calendar invitation organizers who use Google Accounts and prevents future invitations from them. Invitations from organizers who do not use Google require blocking the sender’s email address in Gmail. Announcement on managing unwanted invitations
After blocking, review other existing invitations and manually delete them when needed; Google’s instructions state that existing invitations may remain. Google Calendar blocking instructions Because this article is dated September 16, 2026, note that Google expected the extended rollout to finish on September 18, 2026. The feature may therefore not yet be visible to every account. Extended-rollout timing
Editorial recommendation: Do not treat invitation blocking as fully available before September 18. Check the account, then review older invitations manually instead of assuming that blocking will remove them automatically.
Event colors
Google Calendar provides 24 default colors, allows custom RGB colors to be defined, and offers up to 200 custom colors for use with events across the web, mobile apps, and the Calendar API. This means a palette available for events, not 200 colors inside one event. Custom event colors announcement
Operations teams may create a simple internal color convention, such as meeting type or priority. That is an editorial design suggestion, not a built-in system described by the source.
Pre-adoption checklist
- Check that each feature is visible in the account before adding it to an operating procedure.
- Review secondary-calendar owners and delegate permissions.
- Confirm that an ownership transfer meets the same-organization and Manage Calendars requirements.
- Test private and recurring-event visibility with a test series.
- Assess the effect of suppressing RSVP messages on Google Calendar and external-tool users.
- Review older invitations manually after blocking an unwanted sender.
- Treat colors as a palette available for events, not as a per-event count.
This checklist is an editorial practical recommendation based on the documented limits and features above; it is not a product announcement.