Google is quietly reshaping how organizations manage their Meet hardware, and the latest update is all about control. The company has introduced a new “Video calling” setting that lets administrators decide whether a device can actually join a meeting. It sounds simple, but the implications are big for IT teams juggling dozens—or even hundreds—of conference room setups.

The new toggle lives inside the Admin console, right on each device’s settings page. Flip it on, and the device can join calls as usual. Flip it off, and the hardware essentially becomes a placeholder: instead of showing a meeting interface, it displays the device’s serial number or name along with a short URL. That means admins can keep devices enrolled without worrying about them being used prematurely or in insecure environments.

Google has also added a customer-level enrollment policy. This lets organizations decide whether all new devices should default to video calling being on or off. By default, new devices will still enroll with video calling enabled, but admins can change that if they want a stricter setup process. The idea is to support large-scale rollouts or third-party installers who might not have full admin privileges. In practice, it creates a two-stage process: installers can enroll devices with video calling disabled, and later, once the hardware is in a secure environment, admins can enable calling.

It’s a small tweak, but one that reflects how Google is thinking about enterprise security. Conference room hardware often gets deployed in environments where IT teams don’t have eyes on every step of the process. By giving admins the ability to lock down devices until they’re ready, Google is reducing the risk of rogue connections or misconfigured setups.

The rollout began on February 11, 2026, and will gradually reach all Google Workspace customers with Meet hardware over the following two weeks. For admins, it’s another layer of control in a world where hybrid work has made video conferencing infrastructure more critical—and more complex—than ever.

What’s striking here is how Google is carving out more granular device-level policies. Calendar integration, for instance, has been moved into its own distinct setting, separating it from video calling. That separation suggests Google is anticipating scenarios where organizations might want calendar visibility without enabling calls, or vice versa.

For IT leaders, this update is less about bells and whistles and more about peace of mind. It’s a reminder that in the age of distributed work, even the smallest administrative toggle can make a difference in how secure—and how manageable—your collaboration tools really are.