The News, Explained
Google announced Data Regions support for Workspace Studio on November 20, 2026. Workspace Studio connects tasks in apps such as Gmail and Drive into automated flows. A data region policy specifies the geographic scope for storing or processing designated data. This support applies assigned US or European Union policies to Studio’s core storage and execution infrastructure. Source
Data stored at rest and data processed in use need to be considered separately: where records are kept, and where data is handled while tasks run. The official help page lists user-created Studio flows, custom Skills, starter and step configurations, and run history as covered data. Skills are custom capabilities used in flows. Covered data types and states depend on the Data Regions version. Source
The announcement lists in-region storage for Business Standard and Plus, Enterprise Standard, and Education Standard and Plus. Enterprise Plus and Frontline Plus cover both storage and processing. It also lists the Assured Controls, Assured Controls Plus and Enterprise Data Regions add-ons. Specifying a storage region and being able to constrain processing location therefore need to be understood through the edition’s coverage. Source Source
A dedicated Studio control is added to Data Regions advanced settings in the Admin console. Nonregionalized features are features that process data across regions, and allowing them is the default. The help page instructs administrators to enable processing in the selected storage region before using advanced settings. Settings can apply across the organization or to organizational units, often used for departments, and groups. Source Source
Turning off nonregionalized Studio features restricts Drive starters such as file-change triggers, Forms starters and steps, Tasks steps and webhook steps. A starter initiates an automation; a webhook here sends flow data to an external address. Unsupported items appear greyed out in the builder and are blocked at runtime. Users receive an explanation that administrative policy makes them unavailable, and have no end-user setting to change this. Source Source
AI features depend on two controls. If nonregionalized features are turned off for either Studio or Gemini, AI steps, prompt-based flow creation and Skills are unavailable. Both controls must be on to use generative AI features in Studio. As a hypothetical example, someone planning a flow that starts when a file is added and organizes it with AI needs to consider whether the Drive starter and AI step are each allowed under the applicable policy. Source Source
The announcement date and rollout start are separate. The November 20 post says gradual rollout began November 10 for both Rapid Release and Scheduled Release domains, with up to 15 days for feature visibility. Users outside a Data Region policy, or in organizational units allowing nonregionalized features, retain their Studio functionality. Source
OYOPICK’s Take
We see value in connecting each automation step with where its data is processed. Stored records, starters, AI processing and external connections perform different roles within a flow. If organizations first define their location requirements and understand whether each step fits them, they can make more specific decisions about functionality and governance when adopting automation.
The reason a step becomes greyed out needs to be visible throughout that process. Making the two-control dependency for AI easy to find could help users distinguish a malfunction from an administrative restriction. We hope future guidance makes it easier to see which location policies affect each step across an entire flow.