The ChromeOS Dev channel is being updated to OS version 16733.12.0 (Browser version 151.0.7922.14) for most ChromeOS devices.

1. File a bug

2. Visit our ChromeOS communities

1. General: Chromebook Help Community

2. Beta Specific: ChromeOS Beta Help Community

3. Report an issue or send feedback on Chrome

4. Interested in switching channels? Find out how.

Alon Bajayo

Google ChromeOS

We're introducing a new calendar sharing permission level: “Make changes (see private events as free/busy)”. This allows you to grant someone edit access to your calendar while keeping the details of your private events entirely hidden. This is especially useful for leaders who assign delegates to help them manage their calendars.

Delegates assigned this restricted permission level will only be able to create, delete, and edit non-private events. Private events will appear to delegates as “busy” blocks on the calendar grid, and delegates will not be able to edit or reschedule them. In addition, private events won’t show up in any search results for delegates.

Changes to visibility for recurring events

We’re also introducing changes to the way visibility settings are applied to recurring events.

• Users can no longer make changes to the visibility of a single event in a recurring series. Any changes to visibility will be applied to all events in the series.
• Existing events in a recurring series will be updated to match the strictest visibility setting of any event in that series. In other words, if one event in the series is marked private but the others are not, all events in that series will be changed to private.

Getting started

• Admins: There is no admin control for this feature.
• End users: Users can grant delegates this new permission level in their Calendar settings. Visit the Help Center to learn more about sharing your calendar.

Rollout pace

• Rapid and Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on July 7, 2026

Availability

• Available to all Google Workspace customers, Workspace Individual subscribers, and users with personal Google accounts

Resources

• Google Calendar Help: Share your calendar

 The Stable channel has been updated to 150.0.7871.100/.101 for Windows and Mac and 150.0.7871.100 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log

Earlier this year, we announced Fill with Gemini in Google Sheets, a new AI-powered feature designed to make data preparation and manual entry even easier. Leveraging the capabilities of the AI function in Google Sheets, Fill with Gemini eliminates the need for complex formulas, helping you easily generate text, summarize information, categorize data, or analyze sentiment at scale with generated content appearing directly in the cells you choose.

Previously available in English, Spanish, Portuguese, Japanese, Korean, French, Italian, and German, both Fill with Gemini and the AI function are now expanding to users in Mandarin, Dutch, Malay, Hebrew, Polish, Turkish, Czech, Indonesian, Swedish, Danish, and Norwegian.

Getting started

• Admins: Fill with Gemini is an entry point to the existing AI function. It will be hidden if the Smart features for Google Workspace setting is disabled. Visit the Help Center to learn more about managing Google Workspace smart features for your users.
• End users: You must have Workspace smart features enabled to use Fill with Gemini. Users can trigger Fill with Gemini by dragging a selection or selecting empty cells to see the prompt menu. Visit the Help Center to learn more about filling columns with Gemini.

Rollout pace 

• Rapid Release and Scheduled Release domains: Gradual rollout (up to 15 days for feature visibility) starting on July 7, 2026

Availability

• Business: Business Standard and Plus
• Enterprise: Enterprise Standard and Plus
• Consumer: Google AI Pro and Ultra
• Education Add-ons: Google AI Pro for Education
• AI Add-ons: AI Expanded Access*

*Starting July 15, 2026, users with AI Expanded Access licenses will have higher limits on usage of Fill with Gemini and the AI function in Sheets. 

Resources

• Google Docs Editors Help: Use the AI function in Google Sheets
• Google Admin Help: Set smart features & controls on or off for users

Occupancy counting is now available for Android-based Neat room hardware to help measure how meeting rooms are used. This feature brings the same occupancy counting capabilities found on ChromeOS devices to Android-based hardware.

Understanding room occupancy helps organizations optimize real estate and room design based on user needs. For instance, organizations can track if rooms with older video hardware are being avoided in favor of rooms equipped with better tracking cameras and audio bars.

Admins can review occupancy data in the Google Admin console and optionally download it as a spreadsheet. This feature does not collect or store any personally identifiable information (PII). Because occupancy detection processes data locally on the device, the camera LED indicator may remain off during counting depending on the hardware vendor. Refer to vendor documentation for device-specific information.

Review room booking and occupancy in the Admin console

Getting started

• Admins: This feature will be off by default and can be enabled at the domain, organizational unit (OU), or group level. Visit the Help Center to learn more about turning on occupancy detection.
• End users: There is no end-user setting for this feature.

Rollout pace

• Rapid Release and Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) started on July 6, 2026

Availability

• Available to all Google Workspace customers with Google Meet on Neat AOSP hardware devices. 

Resources

• Google Workspace Admin Help: Turn on occupancy detection
• Google Workspace Admin Help: Track room and device usage with Meet hardware

Today, we are launching a pilot process to expedite the Basic Access application review process. If you have a pending Basic Access application for your Google Ads API developer token, then you can complete brand verification for your Google Cloud project to expedite the reviews for your pending application. With this launch, we aim to reduce the review delays and better meet the significant interest from our developer community for Google Ads API access.

What is brand verification?

Brand verification provides a way for an application developer to verify that they accurately represent their identity and intent as specified by Google API Services User Data Policy. Brand verification is part of the OAuth App verification process, and is an automated self-service option for most developers.

How do I expedite the review process?

If you have a pending Basic Access application for your developer token, then follow these instructions to expedite the review process:

1. Associate your developer token to your Google Cloud project. This step is important; without it we won’t know which Google Cloud project to use as part of the review process.
2. Complete brand verification for your Google Cloud project. If you completed brand verification for your Google Cloud project in the past while using another Google API, you don’t need to repeat the process. If you have more than one Google Cloud project associated with your developer token, you need to complete brand verification only for one project.

Once your Google Cloud project is brand verified, your pending Basic Access application will be reviewed in the next few hours.

Is brand verification mandatory?

Currently, brand verification is optional and is used only as a signal for faster determination of Ads API Basic Access eligibility. This means that

• You may complete the Brand verification process for your Google Cloud project to expedite the review process for your Basic Access application.
• The Google Ads API Compliance team may request some developers with pending Basic Access applications to complete brand verification.

You don’t need to complete brand verification if you already have an approved developer token and aren’t newly applying for Basic Access level.

We will closely monitor the developer experience throughout pilot surveys and use that data to determine the future changes to the application review process for developer token access levels.

 - Anash P. Oommen, Google Ads API Team