Skip to main content

Google Workspace Updates

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

  • Control continuous meeting chat for your organization

    Last year, we launched the ability to continue your Meet conversations in Chat. That rollout will continue this month, with the release to Scheduled Release domains planned to start the week of March 23. In the meantime, we’re excited to introduce a new admin control for this feature In the Workspace Admin console, under Meet Safety Settings, you’ll now see a continuous meeting chat setting that allows you to configure continuous meeting chat behavior for your organization. You can do the following:

    • Set the default state:Choose whether continuous meeting chat is "Default on" or "Default off" for organizational units (OU), configuration groups, or individual users.
    • Control host modifications:Choose whether meeting hosts can change this setting ("Hosts can modify") for their individual meetings, or if the default state is locked ("Hosts cannot modify").

    Set the continuous meeting chat policy for your organization


    This feature gives admins more control to set policy and security preferences in their organization. Now, you can easily:

    • Manage feature training at your organization's pace, or address compliance concerns regarding external message retention and data sprawl.
    • Ensure all in-meeting messages are retained in Google Chat for a specific period of time to meet legal or internal compliance requirements.

    Getting started

    • Admins:This feature will be configured to “Default on” with “Hosts can modify” by default. You can adjust this setting by organizational units (OU), configuration groups, or individual users. Please note that Google Chat must be enabled for your organization to configure continuous meeting chat. Visit the Help Center to learn more.
    • End users:Depending on your admin's configuration, meeting hosts can turn continuous meeting chat on or off in the Calendar event video call options before a meeting starts. If your admin chooses "Hosts cannot modify" this host control will not be visible.

    Rollout pace

    Availability

    • Business:Business Starter, Standard, and Plus
    • Enterprise:Enterprise Starter, Standard, and Plus
    • Other Editions: Frontline Starter, Standard, and Plus; Essentials Starter, Enterprise Essentials, and Enterprise Essentials Plus; Nonprofits

    Resources

  • Better screen scaling for Google Calendar on large monitors

    Google Calendar on the web now offers improved scaling on large, high-resolution monitors. This update provides a clearer overview of your day or week by reducing unnecessary whitespace and better utilizing your available screen space.

    Previously, users with large or high-resolution monitors may have felt that it was difficult to get an overview of the day or week's most relevant events.

    This update means:

    • Better visibility:Calendar events will better fill the available space, giving more room to short meetings.
    • Focused views:The grid will prioritize showing a relevant 12–15 hour range (such as 7:00 AM to 7:00 PM) based on your viewport height.
    • Consistent experience:These improvements apply to both the main Calendar application and the side panel companion view in other Workspace apps (e.g. Gmail).

    Getting started

    • Admins:There is no admin control for this feature.
    • End users:This feature will be ON by default. Users can manually adjust their view preference under Settings > Appearance > Information density. Visit the Help Center to learn more.

    Rollout pace

    • Rapid Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on March 10, 2026
    • Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on April 10, 2026

    Availability

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

    Resources

  • Assign Google Calendars to Google Meet hardware in bulk

    We’re making it easier to manage calendar assignments for your Meet hardware devices. You can now assign or unassign Google Calendars to your Meet hardware devices in bulk by uploading a CSV file. For organizations with a large number of devices, this eliminates the need to assign calendars one by one, saving you significant time and administrative effort.

    The new “assignedCalendarResourceEmail” column in the bulk update CSV file.

    Bulk update device dialogue mentioning the new bulk update calendar assign capability

    When preparing your CSV file, please keep the following in mind:

    • To unassign a calendarfrom a device, simply leave the assignedCalendarResourceEmailcell for that device’s row empty.
    • While a personal calendarcan be assigned to multiple devices, a room calendar resource can only be assigned to one device at a time. To move a calendar resource to a new device using CSV, you must first perform a CSV upload to unassign it, and then a second CSV upload to assign it to the new device.

    Getting started

    • Admins:To use this feature, you’ll need the “Manage calendar assignment” privilege. Without this privilege, any calendar updates in your upload will fail, though other changes (like settings and organizational unit updates) may still be applied. Visit the Help Center to learn more about assigning a Google Calendar to Meet hardware and bulk updating Meet hardware settings.
    • End users:There is no end user impact or action required.

    Rollout pace

    Availability

    • Available for all Google Workspace customers

    Resources

  • New Device ID for Google Meet hardware

    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

  • Updates to meetings made by a delegate user are now sent in the name of the principal

    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

  • Google Workspace Updates Weekly Recap - March 6, 2026

    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.

  • New dynamic data source support for dropdowns in Google Chat apps

    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

  • Improving the connection between Google Calendar events and Google Meet calls

    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

  • 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. Previously, this capability was only available to users with personal Google accounts; this update expands access on web to Gemini users with a work or school account.

    Creating public links to share Gemini conversations can improve collaboration, efficiency, and content sharing. Recipients do not need their own account. This feature lets you share full conversations - including prompts and responses - with a clickable URL.

    Public links that were previously created in the Gemini app will continue to be accessible unless the links are deleted from the Gemini app. Learn how to delete a public link in the Gemini app.

    Google Workspace admins will have a new control to allow users in their organization to share their Gemini conversations with public links.

    Getting started

    • Admins: Public Gemini chat link sharing will be OFF by default and can be enabled at the domain, organizational unit (OU), or group level using a new control in the Admin console. Visit the Help Center to learn more.
    • End users:Visit the Help Center to learn more about sharing your chats in Gemini. If you choose to share a chat, anyone with the link can read the chat, reshare it with others, and, except for chats created with Gems or for users under the age of 18, continue the chat with Gemini Apps on their own. Do not create public links to chat conversations containing confidential information or any data you wouldn’t want to be seen or shared publicly.

    Rollout pace

    Availability

    • Google Workspace customers, Workspace Individual subscribers, and users with personal Google accounts who are signed in to the Gemini app

    Resources

  • 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.

    For some endpoint types, additional information will be logged in addition to the join permission type:

    • For users who asked to join a meeting, the audit event will show which of the other meeting participants admitted them
    • For meeting room hardware devices that joined a client-side encrypted meeting, the audit event will show which user logged in to grant the room access through delegated authentication

    Getting started

    Rollout pace

    Availability

    • Available to all Google Workspace customers

    Resources