View conference room and meeting location details directly on the Google Meet homepage

Earlier this year, we introduced the refreshed Google Meet homepage on the web to help you stay organized and prepared throughout your entire meeting workflow. Starting today, we’re enhancing the Meet homepage experience by displaying conference room and physical meeting locations directly on upcoming meeting cards. For in-office users this update allows them to see where they need to go directly on their Meet landing page, streamlining their workflow before and between meetings.

Key capabilities of this update include:

• Intelligent Room Prioritization: For meetings with multiple rooms across different buildings or campuses (such as all-hands or cross-functional team syncs), Google Meet automatically compares room metadata against the user's Working Location set in Google Calendar. The conference room located in the user's building is moved to the top and highlighted, saving users from having to search through remote room lists. 
• Wayfinding: Clicking or tapping on a conference room opens building wayfinding or campus map links (where configured by administrators), helping users navigate to unfamiliar rooms with ease.
• Google Maps Integration for Physical Locations: For offsite meetings, client visits, or events that specify a street address rather than a conference room, clicking the location opens Google Maps directly for turn-by-turn directions.
• Contextual Visibility: Room and location details are prominently visible on cards for meetings that are "Happening Now" and "Starting Soon" (< 10 minutes). For later meetings, location details appear on hover. If an event has multiple rooms or both a room and an address, hovering reveals an overflow button listing all locations.

Getting started

• Admins: There is no admin control for this feature. Conference room details are automatically populated from the building and room resources configured in the Google Workspace Admin console (under Directory > Buildings and resources).
• End users: There is no end user setting for this feature. Go to the Google Meet homepage on the web to use the enhanced experience. To take full advantage of local room prioritization, users should ensure their working location is set in Google Calendar. Visit the Help Center to learn more about setting your working location.

Rollout pace

• Rapid Release domains: Gradual rollout (up to 15 days for feature visibility) started on September 14, 2026 
• Scheduled Release domains: Gradual rollout (up to 15 days for feature visibility) starting on September 28, 2026

Availability

• Available to all Google Workspace customers and Workspace Individual subscribers.

Resources

• Google Meet: Google Meet Homepage
• Google Meet Help: Use the Google Meet homepage
• Google Calendar Help: Set your working location
• Google Workspace Admin Help: Manage buildings, features, and resources
• Google Workspace Updates Blog: A centralized hub for meeting resources on the new Google Meet homepage

Data regions support for Google Apps Script now generally available

Data regions are critical for helping organizations meet internal compliance, legal, regulatory, and data sovereignty obligations by controlling the geographic location of covered data at rest and through data processing. Expanding these controls to Apps Script allows organizations—including those in highly regulated industries and the public sector—to build, deploy, and automate enterprise workflows with confidence that their script data and executions remain within designated geographic boundaries.

When a data regions policy is applied to an organizational unit or group, Apps Script data storage and runtime execution adhere to the specified region:

• Data at rest: Script project files, code definitions, manifest configurations, trigger metadata, and key-value storage (such as Property Service and Cache Service) are stored within the designated geographic region. 
• Data processing: Script executions, container-bound automations, and associated runtime operations are processed within the selected region.

Note on non-regionalized services:

As Google Apps Script transitions to a regionalized data residency model, non-regionalized Apps Script services will be disabled starting in September 2026 for organizations that turn on the Drive and Docs disablement toggle in data regions advanced settings in the Admin console. Learn more about disabling non-regionalized services.

Enabling Data regions support for Apps Script (Under Drive & Docs)

Getting started

• Admins: Apps Script automatically adheres to your existing organizational data location policies configured in the Admin console under Menu > Data > Compliance > Data Regions.
• To manage advanced controls, such as allowing or disabling features that process data outside designated regions, navigate to Data > Compliance > Data Regions > Advanced settings.
• Visit the Help Center to learn more about choosing a geographic location for your data, what data is covered by a data region policy, and advanced settings for data regions.
• End users: There is no end user setting for this feature. Script project creation and executions will automatically follow the data region policy assigned to the user by their administrator. For custom cloud logging and external services, developers can review recommendations in the Apps Script Cloud Projects guide.

Rollout pace

• Rapid Release and Scheduled Release domains: Available now

Availability

• Enterprise: Enterprise Plus (provides in-region data storage and processing)
• Education: Education Standard and Education Plus (provides in-region data storage only)
• Other Editions: Frontline Plus (provides in-region data storage and processing)

Resources

• Admin Help Center: Select geographic locations for data residency
• Admin Help Center: Data covered by region policies
• Admin Help Center: Configure advanced regional settings
• Admin Help Center: Overview of Assured Controls add-ons
• Developer Documentation: Apps Script overview and guides
• Developer Documentation: Managing Google Cloud Platform projects

Connect to Google Meet hardware with room codes now generally available

Google Meet users can now connect to nearby conference room hardware by entering a 5-character room code on their personal device. Building on the recent Connect Room launch that uses proximity-based detection to identify nearby hardware, this update provides a reliable manual fallback when ultrasound is unavailable or disabled. Users will see a "Connect with room code" button on their device’s pre-call screen, which allows them to enter the alphanumeric code displayed directly on the hardware’s screen.

See our Early Preview announcement for full details.

Getting started

• Admins: This feature will be ON by default and can be disabled/enabled at the device level. We have updated our admin settings for Connect room and related features, visit the Help Center to learn more.
• End users: This feature will be ON by default. Your admin can turn this feature off for devices in your organization.

Rollout pace

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

Availability

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

Resources

• Google Meet Help: Use Connect room feature in Google Meet
• Workspace Updates Blog: Seamlessly join meetings on Google Meet hardware with “Connect room”