This official feed from the Google Workspace team provides essential information about new features and improvements for Google Workspace customers.
rss_feed

We’re replacing the current Device ID (“Legacy ID”) for Google Meet hardware devices with a new Device ID. This new Device ID will be displayed everywhere you currently see the Legacy ID throughout the Google Admin console:

  • The device list, details, history, and videocalling pages (Admin console > Devices > Google Meet hardware)
  • All device-keyed URLs in the Admin console
  • Audit logs and BigQuery exports
  • Bulk upload and download features
  • Device ID filter in Meet quality tool (Admin console > Apps > Google Workspace > Settings for Google Meet > Meet quality tool)

Additional details
  • Bulk Updates: Bulk updating device settings by uploading a file on the device list page will require the new Device ID.
  • Audit Logs: Audit logs (Admin console > Reporting > Audit and investigation) and their BigQuery exports will use the new Device ID for all entries going forward. Existing audit logs created before this change will not be modified.
  • Transitioning to the new ID:
    • During the rollout, you may see different IDs for the same device in different locations
    • For the next 6 months after the rollout, you can use either ID in URLs, bulk uploads, the device list page, and the Meet Quality Tool. The Legacy ID will no longer be supported 6 months after the rollout is complete.

Getting started

Rollout pace

Availability

  • Available to all Google Workspace customers with Google Meet hardware devices

Resources

Read More

In many organizations, executives and senior leaders rely on admins or delegates to oversee their busy schedules. In Google Calendar this can be set up by sharing an executive’s calendar with “Make changes to events” or “Make changes and manage sharing” permissions with a delegate user.

We’re updating how meeting notifications are handled when someone manages a calendar on behalf of another user: Previously, initial invitations created by the delegate appeared to come from the principal, but subsequent updates or cancellations were sent from the delegate’s email.

To provide a more consistent experience for meeting participants, all event-related emails — including cancellations and modifications — will now come from the principal. This change ensures seamless calendar management and prevents confusion for guests who may be unfamiliar with the delegate acting on the principal's behalf.

Getting started

  • Admins: There is no admin control for this feature. Visit the Help Center to learn more.
  • End users: There is no end user setting for this feature. Visit the Help Center to learn more.

Rollout pace

Availability

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

Resources

Read More

Improved join permission logging for Google Meet Audit events

Google Meet Audit event logging for endpoints will now also include the permission type used to grant access to join a meeting. | Learn more about improved join permission logging for Google Meet Audit events.

Workspace admins can allow Gemini app conversation sharing for their organizations

Google Workspace admins can now enable users in their organization to share their Gemini chat conversations by creating public links to share and publish. | Learn more about how Workspace admins can allow Gemini app conversation sharing for their organizations.

Improving the connection between Google Calendar events and Google Meet calls

Google is updating how Google Meet links to Calendar events to ensure meeting artifacts (recordings, notes, and chats) are shared with the correct people.This update solves the "ambiguity" of reused codes, preventing sensitive meeting records from being shared with the wrong participants or lost entirely. | Learn more about how the connection between Google Calendar events and Google Meet calls is improved.

New dynamic data source support for dropdowns in Google Chat apps

Google Chat developers can now use dynamic data sources for dropdown menus, allowing apps to query and filter external databases in real-time as a user types. | Learn more about new dynamic data source support for dropdowns in Google Chat apps.

The announcements above were published on the Workspace Updates blog over the last week. Please refer to the original blog posts for complete details.
Read More

Developers can now build more robust and efficient Google Chat apps using dynamic data sources for dropdown menus. With this update, developers can connect dropdowns to external data sources that query and filter results in real-time as a user types, addressing previous scalability issues caused by dropdown menus being limited to static lists of options. This is particularly useful for workflows that require selecting from thousands of possibilities—such as assigning a ticket in a project management tool or selecting a specific file from a large database.


Key benefits include:

  • Improved searchability: Users can now use fuzzy search to find the correct option quickly, rather than scrolling through long lists or using "find" browser commands.
  • Faster performance: By querying data dynamically, apps avoid the latency issues associated with loading massive static lists.
  • Consistent user experience: The dropdown interface now supports search-as-you-type for both static and remote data sources, providing a smoother experience across all platforms, including web, Android, and iOS.
Developers can also specify a minimum number of characters to trigger a search, ensuring that queries are only sent when enough information has been provided to return relevant results.

Getting started

  • Admins: There is no admin control for this feature.
  • End users: There is no end user setting for this feature.
  • Developers: Developers can implement this by reviewing the updated Chat app developer documentation.

Rollout pace

Availability

  • Available to all Google Workspace customers and Workspace Individual subscribers

Resources

Read More

For each video call, Meet attempts to connect the right Calendar event to determine:

Reusing the same meeting code across multiple events can sometimes lead to ambiguity and unexpected behavior such as meeting artifacts being shared with the wrong guests (or no guests at all). We recently announced a change to reduce this ambiguity by stopping automatically copying Meet codes when duplicating Calendar events.

We are now fixing this ambiguity by having each Meet video call be tied to the initial Calendar event where it was created. This gives predictability and transparency about which guests receive notes, messages in Google Chat, recordings and other details from the meeting.

When users manually paste an old meeting code into a new Calendar event, they’ll see a dialog highlighting that the Meet code is still tied to the initial event. Codes created outside of Calendar (like instant meetings from meet.google.com) will remain unlinked.

For example:

  • If you reuse the meeting code from an old Calendar (Event A) on a new Calendar (Event B), meeting artifacts will only be shared with the host, co-hosts, and guests of the old Calendar event (Event A), and not guests of the new Calendar event (Event B).
  • If you reuse a meeting code created from meet.google.com on a new Calendar event, meeting artifacts will only be shared with the meetings host and co-hosts, and not guests of the new Calendar event.

Warnings shown when reusing a meet code

Additional details
If you use Apple Calendar to create Google Calendar events with a Google Meet meeting code, the code will be updated automatically. This change ensures that each event uses a unique meeting code. Users receive an email informing them about the update.

Getting started

  • Admins: There is no admin control for this feature.
  • End users: There is no end user setting for this feature. Visit the Help Center to learn more.

Rollout pace

Changes to behavior when creating Google Calendar event with meeting code in Apple Calendar
Changes to behavior when reusing meeting code in Google Calendar

Availability

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

Resources

Read More

Useful Links

Join the official community for Google Workspace administrators

In the Google Cloud Community, discuss the latest features with Googlers and other Google Workspace admins like you. Learn tips and tricks that will make your work and life easier. Be the first to know what's happening with Google Workspace.

Learn about more Google Workspace launches

On the “What’s new in Google Workspace?” Help Center page, learn about new products and features launching in Google Workspace, including smaller changes that haven’t been announced on the Google Workspace Updates blog.

Learn about our customers

Discover how a diverse range of organizations, from small businesses and nimble startups to globally recognized Fortune 500 corporations, leverage the collaborative power of Google Workspace. Explore examples of how teams of are streamlining workflows and driving productivity by utilizing Google-Workspace.