Google is making it a lot easier for mixed Google‑and‑non‑Google workplaces to share meeting rooms and other office resources, without forcing everyone onto Google Calendar. This new open beta lets people on third‑party calendars, like Outlook, book Google Workspace resources almost as if they were native to their own system.

The idea targets a very common reality in large companies and multi‑tenant setups: not everyone is on the same calendar platform, but everyone still needs to fight for the same rooms, cars, or shared equipment. Until now, this often meant awkward workarounds—like asking a colleague on Google Calendar to book a room on your behalf, or maintaining duplicate “shadow” calendars in different systems just to avoid double‑booking. With this update, Google is essentially telling IT teams, “Keep your existing calendar setup; we’ll meet you where you are.”

Here’s how it works in practice. Google Workspace admins decide which external people or entire non‑Google domains should be allowed to book specific resources, such as a meeting room or a pool car. Once that’s configured in the Admin console, a non‑Google user can simply invite the resource by email address in their usual calendar tool—no extra plug‑ins, portals, or special accounts needed. If that resource is already set up to auto‑respond, it will accept or decline the booking based on availability and send a confirmation email back to the organizer, just like a normal Google room calendar would.

For organizations running both Google Workspace and Microsoft Outlook, this gets even more powerful when combined with Calendar Interop. With the right configuration, Outlook users can look up Google Workspace rooms by name, see when they’re free or busy, and then book them directly from Outlook’s scheduling interface, instead of manually guessing times or relying on back‑and‑forth messages. The end result is that an Outlook user can treat a Google‑managed room almost like any other Exchange room—search, check availability, and invite it to the meeting.

On the admin side, this feature is off by default, so IT teams stay in full control of who can touch which resources. Permissions are set at the resource level in the Google Admin console, which means a company could, for example, allow a partner’s domain to book only certain guest rooms or shared spaces, while keeping internal‑only rooms restricted. Admins can rely on Google’s existing resource management and calendar‑sharing stack—buildings, features, and resource calendars—to decide how discoverable and bookable each room is, both internally and externally.

From a rollout standpoint, Google says this is an open beta, with a gradual rollout across both Rapid Release and Scheduled Release domains starting April 7, 2026. It’s available broadly across business and enterprise tiers—Business Starter, Standard, Plus; Enterprise Starter, Standard, Plus—as well as education tiers and even Frontline and Nonprofits editions. That wide coverage signals Google sees this as a core capability, not a niche enterprise add‑on.

This move also fits a larger pattern in Workspace: making it easier for outsiders to interact with your organization’s tools without forcing them to create a Google account. Similar concepts already exist in Drive’s visitor sharing, where non‑Google users can collaborate on files with a one‑time identity flow instead of signing up for a new account. Extending this “no account required” philosophy to room and resource booking helps smooth out collaboration with clients, agencies, and partner companies that might never fully move onto Google’s stack.

For end users, the biggest benefit is that they can stay in the calendar app they’re comfortable with while still getting reliable access to shared spaces. Outlook die‑hards don’t have to keep a Google tab open just to book a room, and Google Calendar users no longer need to act as intermediaries or worry as much about double‑booked spaces. For admins and facilities teams, it simplifies governance: there’s one canonical source of truth for each resource—the Google Workspace resource calendar—and external systems simply talk to it in a controlled way.

If your organization currently juggles multiple calendar platforms, this update is essentially an invitation to centralize resource management in Google while still letting teams use the tools they prefer. It won’t magically fix messy processes or bad naming conventions for rooms, but it does remove a big technical excuse for why mixed‑stack companies can’t have a clean, shared booking experience. For hybrid work, cross‑company projects, and office hoteling setups, that kind of low‑friction, cross‑platform booking is exactly the sort of quality‑of‑life upgrade that users notice—even if they never realize it came from a behind‑the‑scenes Google Workspace update.