The rapid transition to working from home during the pandemic was made much easier thanks to Google Meet and other video conferencing software.
For its part, Google has continually updated Meet with new features such as breakout rooms, hand raising, polls and more. However, one of the most requested features the search giant added to Meet last year was the ability to use a custom background.
With a custom background enabled, meeting participants can not only hide their messy rooms but they can also express their personality or interests while in a video call. Google also gave Meet users the ability to blur their background so that other participants wouldn't be able to see what's behind them.
- We've built a list of the best video conferencing software available
- These are the best business webcams for working from home
- Also check out our roundup of the best headsets for conference calls
However, while custom backgrounds can be fun and help alleviate meeting fatigue, they can also be distracting which is why Google has added a new admin setting to Meet to control background replacement in video calls.
Disabling custom and preset backgrounds
In a new Google Workspace update, the search giant has added the ability for admins to enable or disable the use of custom or preset Backgrounds in Google Meet. It's worth noting that this setting is only available in meetings organized by an organizational unit (OU) level.
The new admin setting will determine whether participants can change their background when joining a meeting. This means that if a meeting organizer has turned this setting off, participants will not have the option to change their background regardless of their own personal settings.
For admins this feature will be on by default but it can be disabled at the OU or group level. However, the option will be disabled by default for Education and Enterprise for Education domains.
- We've also rounded up the best office desks and best office chairs
from TechRadar - All the latest technology news https://ift.tt/3t5jbeC
No comments:
Post a Comment