Google Workspace Changes

Google Meet now features automatic language detection to improve the accuracy of transcripts, notes, and captions.

Google Meet is introducing automatic language detection to ensure that meeting transcripts, summarized notes, and recorded captions are as accurate as possible. The system intelligently detects the spoken language once per meeting; if a mismatch with the current settings is found, a nudge appears on-screen allowing users to quickly switch to the correct language. This feature is available for various Business, Enterprise, Education, and Consumer editions and supports English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish.

Automatic language detection in Google Meet to ensure accurate meeting transcripts and notes.

We’re introducing automatic language detection in Google Meet to help ensure your meeting transcripts, summarized notes, and recorded captions are as accurate as possible. Meet now intelligently detects the language being spoken during a session one time per-meeting. If the detected language does not match the current meeting language setting, a nudge will appear on-screen for the user. This prompt allows a quick switch to the correct language, restarting the generation of meeting artifacts in the appropriate tongue to maintain record integrity. As organizations become more global, meetings may be initiated with incorrect default settings. Inaccurate language settings lead to poor quality transcripts and notes that don't reflect the actual conversation. This feature ensures that even if a meeting starts with the wrong language configuration, users can course-correct within seconds to capture every detail accurately.

Google Meet introduces a safeguarded guest admit flow with dual request queues for hosts.

Google Meet is implementing a new safeguarded guest admit flow to help hosts manage join requests (knocking) more efficiently. Requests will now be split into two separate queues, including a second queue for connections that may require closer scrutiny, where the default action is to deny entry. Hosts and co-hosts maintain full control over whether to approve or deny any request regardless of the suggested default.

Introduction of a new safeguarded guest admit flow in Google Meet to assist hosts in managing join requests.

Google Meet is introducing a new safeguarded guest admit flow designed to help meeting hosts efficiently manage requests from users who wish to join meetings. This enhancement provides hosts with two separate queues for join requests, with a new second queue specifically for connections that may require closer review. The default action for requests in this new queue is to deny entry, giving hosts more control and reducing the time and attention needed to handle numerous requests. Hosts and co-hosts retain full control to override suggested actions.

New admin control for continuous meeting chat in Google Meet.

Google Meet has introduced a new admin control within the Workspace Admin console under Meet Safety Settings. This allows administrators to manage the 'continuous meeting chat' feature by setting the default state (Default on or Default off) for organizational units, configuration groups, or individual users, and deciding whether meeting hosts are permitted to modify this setting for their specific meetings.

New admin control for continuous meeting chat in Google Meet

Google Workspace is introducing a new admin control for continuous meeting chat within Google Meet. This feature allows administrators to configure the default state of continuous meeting chat (on or off) for organizational units, configuration groups, or individual users. Additionally, admins can control whether meeting hosts have the ability to modify this setting for their individual meetings. This provides organizations with enhanced control over chat behavior, assisting with managing feature training, addressing compliance concerns, and ensuring message retention in Google Chat.

Admins can now assign or unassign Google Calendars to Google Meet hardware devices in bulk via CSV upload.

Google is introducing a new capability for administrators to manage calendar assignments for Meet hardware devices in bulk. By utilizing a CSV file with the 'assignedCalendarResourceEmail' column, admins can assign or unassign calendars across multiple devices simultaneously, reducing administrative effort for large organizations. Note that while personal calendars can be assigned to multiple devices, room calendar resources are limited to one device at a time, requiring a two-step CSV process to move them between devices.

Tying Google Meet calls to their initial Calendar event to prevent artifact ambiguity

Google Meet is now tying each video call to the initial Calendar event where it was created to ensure predictability regarding who receives meeting artifacts such as Gemini notes, recordings, and Google Chat messages. If a meeting code is reused in a new Calendar event, artifacts will only be shared with the guests of the original event, and users will see a warning dialog when manually pasting an old meeting code.

Improved join permission logging for Google Meet Audit events.

Google Meet Audit event logging for endpoints will now include the permission type used to grant access to join a meeting. For users who asked to join, the audit event will specify which participant admitted them. For meeting room hardware devices joining client-side encrypted meetings, the audit event will identify the user who granted access through delegated authentication.

Improved join permission logging for Google Meet Audit events

Google Meet audit events will now include the specific permission type used to grant access for joining a meeting. For some endpoint types, additional details will be logged, such as which participant admitted a user who asked to join, or which user granted access to meeting room hardware devices joining client-side encrypted meetings through delegated authentication.