[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

3 New updates 

Unless otherwise indicated, the features below are available to all Google Workspace customers, and are fully launched or in the process of rolling out. Rollouts should take no more than 15 business days to complete if launching to both Rapid and Scheduled Release at the same time. If not, each stage of rollout should take no more than 15 business days to complete.

Improved paste values experience in Google Sheets 
Previously, when pasting a number in Google Sheets using Paste special > Values only, the content pasted was only the text from the original range of cells. For example, for the date 9/21/2023, paste values only would paste the date serial number of 45190. To improve upon this feature, the default for paste values for numbers will include values and the number format, meaning all of your numbers will retain their formatting as you are working in Sheets. | Available now to all Google Workspace customers and users with personal Google Accounts. 
Improved paste values experience in Google Sheets
Different certificates for signing and encrypting messages in Gmail 
If your organization uses different certificates for signing and encrypting messages, you can now use the Gmail CSE API to upload different encryption and signature public certificates for each user. | Rolling out to Rapid Release domains now; launch to Scheduled Release domains planned for October 9, 2023. | Available to Google Workspace Enterprise Plus, Education Plus, and Education Standard customers. | Visit the Help Center to learn more about using the Gmail CSE API to manage user certificates. 


Allow certificate mismatches for client-side encrypted messages 
In some cases, the email address associated with a user’s certificate might be different from their primary email address — this is known as a certificate mismatch. Admins can now opt to allow certificate mismatches, which means their end users will be able to decrypt and read messages with a mismatch. It should be noted that we recommend allowing certificate mismatches only when this feature is absolutely required for our organization. | Rolling out to Rapid Release domains now; launch to Scheduled Release domains planned for October 9, 2023. | Available to Google Workspace Enterprise Plus, Education Plus, and Education Standard customers. | Visit the Help Center to learn more about allowing certificate mismatches for client-side encrypted messages in Gmail.


Previous announcements

The announcements below were published on the Workspace Updates blog earlier this week. Please refer to the original blog posts for complete details.


Create, modify, and insert email templates within Groups messages 
When you’re using Groups to send messages, you can save a composed message as a template to reuse in the future. | Learn more about email templates within Groups messages. 

Additional space manager capabilities in Google Chat 
We’re adding two new controls to the list of space manager capabilities in Google Chat that were introduced earlier this year to ensure effective conversations take place in spaces. The new “Manage apps” and “Manage webhooks” options will allow space managers to control the ability of space members to add and remove apps and webhooks to a space. | Learn more about new space manager capabilities. 

Easily link to a specific message in Google Chat 
Building upon the recent updates in Google Chat, such as message views, in-line replies and larger spaces, we’re introducing message linking, an additional feature that helps teams collaborate more effectively. | Learn more about message linking. 

Easily add or remove groups of members to a space in Google Chat 
We’re introducing a new app for Google Chat called Bulk Member Manager that enables space managers and space members, who have permission to manage members, to easily add or remove members to or from a space in bulk. | Learn more about the Bulk Member Manager app. 

The next phase of digital whiteboarding for Google Workspace 
In late 2024, we will wind down the Jamboard whiteboarding app as well as continue with the previously planned end of support for Google Jamboard devices. | This update impacts all Google Workspace customers who use the Jamboard app or 55-inch Jamboard device. | Learn more about the winding down of the Jamboard whiteboarding app. 

Updates regarding the transition from spaces organized by topic to in-line threading in Google Chat 
In 2022, we introduced in-line threading for Google Chat and since March 2023, all newly created spaces in Google Chat are in-line threaded by default. On September 30, 2023, we will begin taking the next step toward a single, streamlined flow of conversation in Google Chat: all existing spaces organized by conversation topic will be upgraded to the in-line threaded experience. We’d like to share more information regarding the migration, what to expect, as well as what’s next for Google Chat. | Learn more about in-line threading in Google Chat. 

Client-side encryption in Gmail is now available on mobile devices 
We’re expanding client-side encryption in Gmail to Android and iOS devices, so you can read and write encrypted messages directly from your device. | Learn more about client-side encryption in Gmail on mobile devices.

Beginning September 30, 2024: third-party apps that use only a password to access Google Accounts and Google Sync will no longer be supported 
Google Workspace will no longer support the sign-in method for third-party apps or devices that require users to share their Google username and password. | Learn more about Access to Less Secure Apps (LSA).



Completed rollouts

The features below completed their rollouts to Rapid Release domains, Scheduled Release domains, or both. Please refer to the original blog posts for additional details.

Rapid Release Domains:



Labels: , , , ,

[Update - October 15, 2024]: Rollout for this update has been paused for the remainder of the year and will resume in January 2025. In the interim, GoogleSync and Less Secure Apps will continue to function as usual. We’ll share another update here when rollout resumes.


What’s changing 
As part of our commitment to user safety, Google Workspace will no longer support the sign-in method for third-party apps or devices that require users to share their Google username and password. This antiquated sign-in method, known as Less Secure Apps (LSAs), puts users at an additional risk since it requires sharing Google Account credentials with third-party apps and devices that can make it easier for bad actors to gain unauthorized access to your account. 


Instead, you’ll need to use the option to Sign-In with Google, which is a safer and more secure way to sync your email to other apps. Sign-in with Google leverages industry standard and more secure OAuth method of authentication already used by the vast majority of third-party apps and devices. 


We previously announced this change in 2019, and are now ready to share an updated timeline regarding this change:


Access to Less Secure Apps (LSA) will be turned off in two stages: 
  1. Beginning June 15, 2024:
    • The LSA settings will be removed from the Admin console and can no longer be changed. Enabled users can connect during this time, but disabled users will no longer be able to access LSAs. This includes all third-party apps that require password-only access to Gmail, Google Calendar, Contacts via protocols such as CalDAV, CardDAV, IMAP, SMTP, and POP. 

    • The IMAP enable/disable settings will be removed from users’ Gmail settings.

    • If you’ve been using LSAs prior to this date, you can continue using them until September 30, 2024.

  2. Beginning September 30, 2024:

As part of this change, Google Sync will also be sunsetted: 
  • Beginning June 15, 2024: New users will not be able to connect to Google Workspace via Google Sync.
  • September 30, 2024: Existing Google Sync users will not be able to connect to Google Workspace. Here is how you can transition your organization off Google Sync. To find Google Sync usage in your organization, please go to the Admin Console, navigate to Devices > Mobile & Endpoints > Devices, and filter by Type: Google Sync.


See below for more specific guidance for admins, end users, and developers regarding this change.


Who’s impacted
Admins and end users


Getting Started
Admins
Preparing your end users
In order for your end users to continue using these types of apps with their Google Workspace accounts, they must switch to a more secure type of access called OAuth. You’ll receive more information via email with affected users in your organization in the coming months. We recommend that you share the user instructions (included below) to help them make the necessary changes. 


Mobile Device Management (MDM) Impact
If your organization uses a mobile device management (MDM) provider to configure IMAP, CalDAV CardDAV, POP or Exchange ActiveSync (Google Sync) profiles, these services will be phased out according to the timeline below:
 

June 15, 2024

MDM push of password based IMAP, CalDAV, CardDAV, STMP, POP and Exchange ActiveSync (Google Sync) will no longer work for customers who try to connect to an LSA for the first time.

If you use Google Endpoint Management, you will not be able to turn on "Custom Push Configuration" settings for CalDAV and CardDAV.

September 30, 2024

MDM push of password based IMAP, CalDAV, CardDAV, SMTP and POP will no longer work for existing users. Admins will need to push a Google Account using their MDM provider, which will re-add their Google accounts to iOS devices using OAuth. 


MDM push of password based Exchange ActiveSync (Google Sync)  will no longer work for existing users. Admins will need to push a Google Account using their MDM provider, which will re-add their Google accounts to iOS devices using OAuth.


If you use Google Endpoint Management, “Custom push configuration-CalDAV” and “Customer push configuration-CardDAV” (more details about the settings here) will stop being effective. 



Scanners and other devices
If you have scanners or other devices using simple mail transfer protocol (SMTP) or LSAs to send emails, you’ll need to either: configure them to use OAuth, use an alternative method, or configure an App Password for use with the device. 


End users
If you are using an app that accesses your Google Account with only a username and password, take one of the following actions to continue to access your email, calendar, or contacts. If you do not take one of the following actions by September 30, 2024, you will begin receiving an error message that your username-password combination is incorrect and you will not be able to log in. 


Email Applications

Outlook 2016 or Earlier

Move to Microsoft 365 (formerly known as Office 365, a web-based version of Outlook) or Outlook for Windows or Mac, both of which support OAuth access.

Alternatively you can use Google Workspace Sync for Microsoft Outlook. 

Thunderbird or another email client

Re-add your Google Account and configure it to use IMAP with OAuth.

The mail app on iOS or MacOS, or Outlook for Mac and use only a password to login

You’ll need to remove and re-add your account. When you add it back, select “Sign in with Google” to automatically use OAuth.

MacOS:

iOS:




Calendar Applications
  • If you use an app that uses password based CalDAV to give access to your calendar, switch to a method that supports OAuth. We recommend the Google Calendar app [Web/iOS/Android] as the most secure app to use with your Google Workspace account.
  • If your Google Workspace account is linked to the calendar app in iOS or MacOS and uses only a password to login, you’ll need to remove and re-add your account to your device. When you add it back, select “sign in with Google” to automatically use OAuth. Read more.


Contacts Applications
  • If your Google Workspace account is syncing contacts to iOS or MacOS via CardDAV and uses only a password to login, you’ll need to remove your account. When you add it back, select “sign in with Google” to automatically use OAuth. Read More.

  • If your Google Workspace account is syncing contacts to any other platform or app via CardDAV and uses only a password to login, switch to a method that supports OAuth.


All Other Applications
If the app you are using does not support OAuth, you will need to switch to an app that offers OAuth or create an app password to access these apps.



Developers
To maintain compatibility with Google Workspace accounts, update your app to use OAuth 2.0 as a connection method. To get started, follow our developer guide on using OAuth 2.0 to access Google APIs. You can also refer to our guide on OAuth 2.0 for mobile & desktop apps. 


Users with personal Google accounts: In the coming weeks we will be removing the IMAP enable/disable toggle from your Gmail settings. IMAP access is always enabled over OAuth and your current connections will not be impacted. No action is required of users. 

Availability
  • This change impacts all Google Workspace customers.

Resources

Labels: , ,

What’s changing 
We’re expanding client-side encryption in Gmail to Android and iOS devices, so you can read and write encrypted messages directly from your device. This allows your users to work with your most sensitive data from anywhere on their mobile devices while adhering to compliance and regulatory requirements. The Gmail mobile apps support encrypted mail natively, so users don't need to download multiple apps, or navigate to an external portal, to access their encrypted messages. 


While Workspace encrypts data at rest and in transit by using secure-by-design cryptographic libraries, client-side encryption ensures that you have sole control over encryption keys and access to your data. Client-side encryption ensures sensitive data in the email body and attachments are indecipherable to Google servers — you retain control over encryption keys and the identity service to access those keys. For more information, check out our original announcement and the Workspace blog.


Getting started
  • Admins: Admin will need to enable the Android and iOS clients in the CSE admin interface in order for users to have access. This can be done in the Admin Console by going to Security > Access and data control > Client-side encryption > Identity provider configuration. 
  • End users: To add client-side encryption to any message, click the lock icon and select additional encryption, and compose your message and add attachments as normal. Visit the Help Center to learn more about using client-side encryption for Gmail.



Labels: , , , ,

What’s changing 
In 2022, we introduced in-line threading for Google Chat and since March 2023, all newly created spaces in Google Chat are in-line threaded by default. 


On September 30, 2023, we will begin taking the next step toward a single, streamlined flow of conversation in Google Chat: all existing spaces organized by conversation topic will be upgraded to the in-line threaded experience. We’d like to share more information regarding the migration, what to expect, as well as what’s next for Google Chat. 


Who’s impacted 
Admins and end users


Why it’s important
Whether it’s a 1:1 conversation  or a space, Google Chat plays a critical role in collaborating and communicating. Our goal is to continue evolving Chat to best serve our users and keep teams productive and connected. 


As such, we’ve heard from our customers that the way conversations were structured in spaces could be improved. Specifically, users found topic-based conversations to be restrictive and tricky to navigate. With topic-based conversations users would struggle to keep track of individual topics as new replies were added, and often find themselves scrolling back through threads to locate relevant topics.. Over time, topic threads have become noisier and more complex for many users.


What became clear was the need for a continuous conversation flow. In-line threading allows users to reply to any message and create a discussion separate from the main conversation and users have reported a much higher satisfaction rate as compared to topic-based spaces. Users can also follow specific threads, whereby they’ll receive notifications for replies and @ mentions in that thread, helping to cut through clutter and stay on top of what matters most.


What to expect during the upgrade period
Beginning September 30, 2023 we will begin upgrading conversations grouped by topic to in-line threading. We anticipate this change to be completed by March 2024. 


In order to minimize disruptions on day-to-day work, we will do our best to initiate upgrades during off-peak times on weekends. Should you be using Chat during these upgrades, spaces that are being upgraded will be inaccessible for a few minutes. Admins can use this form to specify a specific month and whether they prefer the upgrade to take place on weekdays or weekends. Please note this will be on a best effort basis and this form must be submitted by October 15, 2023. Based on the preference selected by a customer, we’ll choose one of the upgrade windows on a weekday or a weekend in the selected month and upgrade all the eligible spaces during off-peak hours. 

Prior to the upgrade
A minimum of two weeks prior to the upgrade taking place, a banner will be displayed in impacted spaces notifying users about the impending change. Users will be able to click through to the Help Center for more information.


During the upgrade
As mentioned above, we plan to execute these changes during off-peak times to help minimize disruption. If you’re using an impacted space when the upgrade commences, most functions such as sending and receiving messages will be inaccessible. Typically, this will only last for a few minutes, after which users simply need to refresh the browser tab to access and use the newly upgraded space. Other direct messages, group conversations and in-line threaded spaces will not be impacted and will remain accessible during the upgrade



After the upgrade 
Once the upgrade is complete, the space will use the in-line threaded model. Messages sent before the upgrade will be retained, and will be arranged chronologically, instead of by topic. There will also be a separator titled “Begin New Topic” to indicate every time a new topic was started. 

In some cases, when people have responded on older topics, the new chronological order takes precedence. This means that messages may not appear next to the original topic, but rather according to their timestamp. When this occurs, the new response will quote the last corresponding message that it is replying to, as seen in the image below. 

You’ll also see a separator between the last message sent before the migration, and a message indicating that the space has been upgraded to a space with in-line replies. Going forward, all new messages will feature in-line threaded functionality. 


More new ways to work with threads
To further elevate the in-line threading experience, we’ll be introducing several new features during the remainder of the year and into 2024. Here’s a preview of some of those features — be sure to subscribe to the Workspace Updates blog for the latest updates on availability. Meanwhile, please refer to this post for even more features coming to Google Chat. 


Resizable threads panel
You’ll be able to easily resize the threads sidebar to best suit your screen size or increase the focus on threads most important to you.


Home shortcut 
“Home” is the place to manage and catch up on your Chat messages. Messages from your followed threads will be shown in Home. You can also filter to only see your followed threads and unread conversations. You’ll be able to open a conversation or reply from the Home view.

Select "Home" from the sidebar. 






You can choose to get notified for all messages, and automatically follow all threads within a space ensuring you don’t miss any updates.


Thread participants 
You will be able to see avatars of users that have replied to a thread to get better context and decide whether the thread is relevant to you.


Getting started

Availability
  • This update impacts all Google Workspace customers 

Resources



Labels: ,

What’s changing 
In late 2024, we will wind down the Jamboard whiteboarding app as well as continue with the previously planned end of support for Google Jamboard devices. For those who are impacted by this change, we are committed to help you transition: 
  • We are integrating whiteboard tools such as FigJam, Lucidspark, and Miro across Google Workspace so you can include them when collaborating in Meet, sharing content in Drive, or scheduling in Calendar. 
  • Further, we’re bringing these whiteboard solutions to the Series One Board 65 and Desk 27 devices by Avocor, so you can visually collaborate using a physical device and stylus. 
  • We will provide a retention and migration path for Jamboard data so you don’t lose any of the collaborative work that’s been created within your organization. 

Admins of impacted Google Workspace customers will receive more detailed information and instructions via email. We’ll continue to provide reminders here on the Updates Blog throughout this process as well.


Who’s impacted
Admins and end users


Why it’s important
We’re committed to partnering with industry-leading companies to bring the most innovative collaboration experiences to Google Workspace. We’ve heard from our customers that whiteboarding tools like FigJam by Figma, Lucidspark by Lucid Software, and the visual workspace Miro help their teams work better together — specifically, the advanced features they offer such as infinite canvas, use case templates, voting, and more. Based on this feedback, we’ve decided to leverage our partner ecosystem for whiteboarding in Workspace and focus our efforts on core content collaboration across Docs, Sheets, and Slides. 


Whiteboarding capabilities in the conference room or classroom
Earlier this year, our partner, Avocor, delivered two next-generation video conferencing and whiteboarding devices, the Series One Board 65 and Desk 27, to succeed the original Jamboard device. With built-in Google AI features, studio-grade audio, and seamless video conferencing through Google Meet, these devices are designed for immersive team collaboration.
 
Today, we’re announcing that FigJam, Lucidspark, and Miro will create integrations for these devices, with expected delivery at the end of 2023 and early 2024 — we’ll keep you posted on the availability here on the Workspace Updates blog. Soon you’ll not only have a choice of three robust third-party whiteboarding experiences inside a Meet call, you’ll also have new options to use them outside a call as standalone whiteboarding tools on the Board 65 and Desk 27.


Transition timeline
Jamboard device: 
  • All Jamboard device license subscriptions (including education licenses) will end on September 30, 2024. If you have an upcoming 12-month subscription renewal, you will have the ability to renew your license subscription for a term that will end on September 30, 2024, at a prorated cost.  

  • If you need to back up any Jamboard device event logs from the Admin console, please do so before September 30, 2024. After this date, you will no longer be able to manage Jamboards from the Admin console and we will begin to delete device event log data.

  • October 1, 2024, the 55-inch Jamboard device will reach its Auto Update Expiration (AUE) and will no longer receive security and feature updates or customer support from Google Workspace. At this time, we will also remove Jamboard device management from the Admin console, leaving the device with limited functionality. Our FAQ page contains details on how you can continue to use your 55-inch Jamboard device beyond its AUE date.

  • Those looking for an alternative to the 55-inch Jamboard device can upgrade to the Google Meet Series One Board 65 and Desk 27 devices by Avocor. Both devices will have integrations with our partners’ whiteboarding software to replace the Jamboard app. We will follow up as we approach the AUE date with reminders and updates.

Jamboard app
  • Starting October 1, 2024, you’ll no longer be able to create new or edit existing Jams on any platform, including the web, iOS, and Android. 
  • Between October 1, 2024, and December 31, 2024, the app will be placed in “view-only” mode, during which time you will still be able to backup your Jam files. Learn more.
  • On December 31, 2024, we will wind down the Jamboard application, meaning your users will no longer be able to access their Jam files and Jam files will be permanently deleted. In the coming months, we’ll provide Jamboard app users and admins clear paths to retain their Jamboard data or migrate it to FigJam, Lucidspark, and Miro within just a few clicks, well before the Jamboard app winds down in late 2024. Review how you can generate a list of your Jamboard active users. Also, have your users download their Jam files
Additional details
    We also understand the unique needs of educational institutions, so we’ve worked with Figjam by Figma, Lucidspark by Lucid software, and the visual workspace Miro to provide whiteboarding capabilities that cater to students and educators, whether they’re in primary school, secondary school, or higher education. To learn more about each offering, see which is best for your educational institution, and get guidance and resources for using these tools, please visit the Help Center. We will also work directly with educational institutions to compensate them for their Jamboard devices.

    Getting started

    Availability
    • This update impacts all Google Workspace customers who use the Jamboard app or 55-inch Jamboard device.

    Resources

    Labels: ,

    What’s changing 
    We’re introducing a new app for Google Chat called Bulk Member Manager that enables space managers and space members, who have permission to manage members, to easily add or remove members to or from a space in bulk. 

    In addition to the new membership search feature and the ability to add up to 50,000 members to spaces in Google Chat, this update will help you better organize people, topics, and projects to help ensure effective conversations take place in spaces.
    Easily add or remove groups of members to a space in Google Chat
    Getting started 
    • Admins: Admins can enable or disable users from adding Chat apps to their spaces by going to the Admin console > Apps > Google Chat > Chat apps access settings. Visit the Help Center to learn more about optimizing Chat spaces for your organization. 
    • End users: 
      • All space managers can add members using the Bulk Member Manager app. A space manager can grant permission for a space member to add other members by going to the space menu > Space settings > Access > selecting the All members option under Who can manage members and groups. If this is granted, a space member can use the Bulk Member Manager app to add members. 
      • To use Bulk Member Manager, open the space that you want to add or remove members to/from > add the app to the space > type one of the following slash commands: 
        • “/addDialog” to add members by copy/pasting email addresses. The app will guide you through the process of adding members. 
        • “/removeDialog” to remove members by copy/pasting email addresses. The app will guide you through the process of removing members. 
        • “/addCsv” (with a .csv attachment) to add members. 
        • “/removeCsv” (with a .csv attachment) to remove members 
      • Visit the Help Center to learn more about using the Bulk Member Manager app.
    Rollout pace 
    • This feature is available now for all Google Workspace customers 
    Availability 
    • Available to all Google Workspace customers 
    Resources 
    Labels: ,

    This announcement is part of Google Cloud Next ‘23. Visit the Workspace Blog to learn more about the new Google Chat. 

    What’s changing

    Building upon the recent updates in Google Chat, such as message views, in-line replies and larger spaces, we’re introducing message linking, an additional feature that helps teams collaborate more effectively. 


    To generate links to messages easier so that others can reference a particular topic or announcement, we’ve added a “Copy link” option for all messages posted in spaces, group messages and direct messages. Once the link is sent and clicked by a colleague, they will be taken to the original message within Chat as long as they have access to the conversation or space.

    Easily link to a specific message in Google Chat

    Getting started 
    • Admins: There is no admin control for this feature. 
    • End users: 
      • To generate a link to a message, hover over the message and click the three-dot menu > select ‘Copy link” > paste the link within the conversation or space of your choice.
        • Users who don’t have access to a specific space will receive an error message upon clicking the link to a message in a space they do not belong to 
      • Visit the Help Center to learn more about linking to a specific message. 
    Rollout pace 
    Availability 
    • Available to all Google Workspace customers and users with personal Google Accounts 
    Resources 
    Labels: ,

    What’s changing 
    We’re adding two new controls to the list of space manager capabilities in Google Chat that were introduced earlier this year to ensure effective conversations take place in spaces. The new “Manage apps” and “Manage webhooks” options will allow space managers to control the ability of space members to add and remove apps and webhooks to a space. 
    The new “Manage apps” and “Manage webhooks” options


    We’re also making the following improvements to enhance the overall experience of spaces in Chat: 
    • An updated “@” mentions dialog notification that explains why a specific user or an app cannot be added to a space. 
    An updated “@” mentions dialog notification

    • A new full screen view on web that shows space managers all installed apps and webhooks within a space. 
    A new full screen view on web
    Getting started 
    Rollout pace 
    Availability 
    • Available to all Google Workspace customers 
    Resources 
    Labels: , ,

    What’s changing 
    When you’re using Groups to send messages, you can save a composed message as a template to reuse in the future. 

    Directly in Groups, you can create and save messages as a template. Templates can also be deleted.


    Who’s impacted 
    End users 


    Why you’d use it 
    We know users rely heavily on sending messages from Groups, and often these messages closely resemble one another with only specific information requiring updates. Now, instead of typing the same message from scratch, you can compose and save your reply as a template, saving you time and accelerating your workflows. Some examples include: 
    • Saving time on a new lead introduction by filling in only critical details, such as the recipient name and one sentence pitch.
    • As a teacher, create a template to quickly share daily homework assignments day after day.
    • When sending project updates, use a template to avoid the trouble of creating status reports from scratch.

    Getting started 
    • Admins: There is no admin control for this feature.
    • End users: Visit the Help Center to learn more about using email templates in Groups. Note that templates are specific to individual users and are not shared across other Group owners, managers, or members. 

    Rollout pace 

    Availability 
    • Available to all Google Workspace customers and users with personal Google Accounts 

    Resources
    Labels: , ,

    New updates 

    There are no new updates to share this week. Please see below for a recap of published announcements. 


    Previous announcements

    The announcements below were published on the Workspace Updates blog earlier this week. Please refer to the original blog posts for complete details.


    Find and install third-party add-ons directly within Google Meet 
    You can now find, install, and use third-party applications all without having to leave Google Meet. | Learn more about third-party add-ons for Google Meet.

    Add Google Groups to spaces in Google Chat 
    We’re introducing the ability for space managers and users with the permission to manage members to add Google Groups to a space. With this update, the group members are automatically added to a space and any changes to the group's membership, such as adding and removing members, are also automatically reflected in the space. | Learn more about Google Groups in spaces. 

    Collaborate more seamlessly with live pointers in Google Slides 
    To boost collaboration in Google Slides, we’re introducing live pointers, a new feature that allows you and your colleagues to see each other’s mouse pointers in real-time. With this update, co-creators can easily point out specific text or visual elements within a Slide in order to highlight important information and content. | Learn more about live pointers in Slides. 

    Pair your video tile in Google Meet to improve accessibility for users with language interpreters 
    We’re introducing tile pairing for Google Meet, which will allow you to pair your video tile with another meeting participant's tile. Once you pair your tile, other meeting participants will see both tiles shown next to each other. Both pairing partners will have their borders outlined in blue when speaking. Tile pairing will be indicated in the meeting captions as well. | Learn more about pairing tiles in Google Meet.

    Differentiate messages better with additional modernizations in Google Chat 
    We’re introducing message bubbles to enable users to more easily differentiate incoming versus outgoing messages in the Chat message stream. | Learn more about message bubbles in Chat. 

    Turn Q&As on or off for Google Meet livestream viewers 
    Earlier this year, we announced that meeting hosts can now enable Q&A and poll features, which previously were only offered in traditional Meet meetings. Beginning this week, meeting hosts can turn Q&A on and off for livestreams. | Learn more about Q&As in Google Meet.

    Additional improvements for monitoring Google Meet hardware issues in the Admin console
    Recently, we announced the ability to detect and monitor several additional Google Meet hardware issues from the Admin console. Now that ChromeOS M108 has rolled out to Meet hardware devices, we’re sharing an update on the rollout of some of those features. | Learn more about improvements for monitoring Google Meet hardware issues. 


    Completed rollouts

    The features below completed their rollouts to Rapid Release domains, Scheduled Release domains, or both. Please refer to the original blog posts for additional details.


    Rapid Release Domains:

    Labels: ,

    What’s changing
    Recently, we announced the ability to detect and monitor several additional Google Meet hardware issues from the Admin console. Now that ChromeOS M108 has rolled out to Meet hardware devices, we’re sharing an update on the rollout of some of those features, including new options to fine tune your alerts: 

    • Missing display issues began rolling out in the Admin console on September 21 and may take up to 10 days to go into effect on all domains. 
    • You will be able to select which specific peripheral issue types you want to be alerted about from a new Admin console setting that also began rolling out on September 21 and may take up to 10 days to go into effect on all domains. If you don’t want to receive display alerts (or any other type of peripheral issues), you can opt out using the new setting. Note that the setting can be modified as soon as it appears in your Admin console, but it won’t actually go into effect until October 11. 
    • Unless you’ve turned them off using the aforementioned setting, you will begin seeing email alerts for missing display issues beginning October 11. Note that it may take up to 10 days for settings to go into effect on all domains.
    Monitoring Google Meet hardware issues, like devices going offline or missing cameras, is crucial to ensuring a smooth meeting experience for your users. We hope this update continues to make it easier and faster for admins to be alerted of issues in their fleet and quickly remedy them. See our original announcement for more information. 


    Getting started 
    • Admins: 
      • To view these new issues, you can monitor the status of your peripherals in the Google Meet hardware Admin console.
      • Missing display alerts will begin being sent by email or SMS on or soon after October 11.
      • The new Peripheral issue types setting will go into effect on or soon after October 11. If you want to disable any specific peripheral issue types, be sure to change it ahead of this date. 
    Rollout 
    Missing display issues in the Admin console and peripheral issue type setting: 
    Configurability of peripheral email alerts by issue type: 

    Availability
    • Available to all Google Workspace customers with Google Meet hardware devices 
    Resources 
    Labels: , ,