Google announced on November 20, 2026 that Google Workspace Studio now supports Data Regions and that the support is generally available. Core Studio execution and storage now follow the US or EU data region policy you assign, and a new Workspace Studio control in the Data Regions advanced settings decides whether users in a region can still use steps and generative AI that are not yet regionalized. To start, open the Admin console, go to Menu > Data > Compliance > Data regions, and check what your policy already covers.
What Workspace Studio Data Regions is
Data Regions is the Google Workspace admin feature that lets an organization choose where covered data is stored at rest (United States or Europe) and, on higher editions, where it is processed in use. Workspace Studio is the Google Workspace tool for building automated flows (starters, steps and, with Gemini, AI steps). Until this launch, Studio data was not described as following that policy. According to Google's announcement, the change is that "core Workspace Studio execution and storage backends", including the integrations with Gmail, Google Drive, Google Docs, Google Sheets, Google Calendar, Google Meet and Google Chat, follow the assigned US or EU data region policy.
Google's help page "Data covered by data regions" lists what that means for Studio: the covered data is "User-created flows, custom skills, starter and step configurations, and run history." It is covered at rest under all Data Regions versions, and during processing only under Enterprise and Assured Controls Data Regions.
Not every part of Studio is regionalized yet. The announcement adds a Workspace Studio control to the Data Regions advanced settings. It determines whether users in a data region can access non-regionalized steps and generative AI. By default the feature is on and non-regionalized features stay enabled.
Who it is for and availability
The announcement was published on November 20, 2026. Google says the rollout started on November 10, 2026 for Rapid Release and Scheduled Release domains, and that feature visibility can take up to 15 days. It is aimed at organizations with data residency requirements, for example a company that promised customers US-only or EU-only storage.
| Edition or add-on | What Google lists for Workspace Studio |
|---|---|
| Business Standard, Business Plus | In-region storage only |
| Enterprise Standard | Storage only |
| Enterprise Plus | Storage and processing |
| Education Standard, Education Plus | Storage only |
| Frontline Plus | Storage and processing |
| Assured Controls, Assured Controls Plus, Enterprise Data Regions (add-ons) | Listed as eligible |
Google's help pages give no Workspace Studio price. Data Regions is a feature of the editions above or an add-on, and the announcement does not list a separate price. Regions available in the Admin console are United States, Europe (labeled "Europe" in the console for the EU) or No preference. The announcement does not state any India-specific region; the policy choices are US or EU. Admins in the US and India can both use it if they hold an eligible edition.
Requirements
- An eligible edition from the table above. Google's page on choosing a geographic location says users without a supported edition are not covered, even if you apply a policy to their organizational unit.
- The "Data Regions Settings" administrator privilege. Viewing status reports needs the "Data Regions Reporting" privilege.
- For different regions per department (organizational unit) or group: Frontline Plus, Education Standard or Plus, Enterprise Plus or Enterprise Essentials Plus, as that page lists.
- For the advanced settings: Google's advanced-settings page says the menu appears only if you have Enterprise Data Regions, and lists Frontline Plus, Enterprise Plus and Enterprise Essentials Plus as supported editions. To change settings for specific organizational units or groups you need Frontline Plus, Enterprise Plus or a Data Regions add-on.
- To use the processing controls, turn on Data processing first: check "Process data in the region selected for data at rest".
The editions on the announcement and on the advanced-settings help page are not identical (for example, the announcement lists Business and Education editions for storage only, while the advanced-settings page lists three editions). Plan against the stricter list and check which options you actually see in your Admin console.
How to set Data Regions for Workspace Studio, step by step
Step 1: Set where data is stored
Steps from Google's "Choose a geographic location for your data" page:
- If one region does not fit all users, place users in an organizational unit (department-level settings) or in a configuration group (settings that cut across departments). Group settings override organizational unit settings.
- In the Admin console, go to Menu > Data > Compliance > Data regions.
- Optionally select an organizational unit or configuration group.
- Click Region, then Data at rest, select a region and click Save.
- For child organizational units, click Override first. To revert, click Inherit (or Unset for a group).
Step 2: Set where data is processed (eligible editions only)
- On the same page, click Data processing.
- Check "Process data at your selected data at rest region" and click Save.
Google's advanced-settings page words this checkbox as "Process data in the region selected for data at rest". The two pages differ slightly in wording; use the label you see in the console.
Step 3: Decide on non-regionalized Workspace Studio features
Google's "Set up advanced settings for data regions" page lists these steps:
- In the Admin console, go to Menu > Data > Compliance > Data regions > Advanced settings. The announcement also gives the path Account > Data Regions > Advanced Settings.
- Click the service. Google Workspace Studio is among the services you can control, with Calendar, Drive and Docs, Gmail, Chat, Meet, and the Gemini app and Gemini in Google Workspace apps.
- Select the top organizational unit to apply the setting to all users, or a child organizational unit or a group.
- Choose one option: "Enable features that may process data across multiple regions" (on by default; no change to the user experience) or "Turn off features that may process data across multiple regions".
- Click Save. For a child organizational unit, click Override first.
The settings can be applied at the domain, organizational unit or group level, per the announcement.
Step 4: Verify
Security admins can verify regional compliance with the Security Investigation Tool, according to the announcement. Google's page on choosing a location says status of data region storage can be viewed within 24 to 48 hours of a policy change on Frontline Plus or Enterprise Plus, and that advanced reports, which include processing, require Assured Controls.
How to turn it off or go back
Set the advanced-settings control back to "Enable features that may process data across multiple regions", or click Inherit on the organizational unit. Google notes that if you leave a control off, its features will turn on automatically once they are regionalized.
Limitations
When non-regionalized processing is turned off for Studio, the announcement lists these effects:
| Area | What happens |
|---|---|
| Integrations | Google Tasks, Google Forms, Gemini Notebook, Webhooks and Drive event triggers are greyed out in the builder and blocked at runtime |
| AI | AI steps, natural language flow generation and Skills are disabled |
| Generative AI access | Both the Studio control and the Gemini in Google Workspace control must be on to use generative AI in Studio |
| End users | No user-level setting; affected users see a banner saying the unsupported steps or AI tools are unavailable due to administrative policy |
The advanced-settings page describes the same loss as AI features and steps (including creating flows from a prompt), Google Drive, Google Forms and Google Tasks starters and steps, and the Send a webhook step. Google recommends weighing the tradeoffs first, because turning these features off can remove familiar functionality and cause unexpected behavior. Existing flows that use blocked steps may stop working; test in a pilot organizational unit first.
General Data Regions limits from Google's pages:
- Selecting a region does not improve performance or network access, and users may see higher latency when sharing across regions or traveling.
- Gemini Notebook (formerly NotebookLM) is explicitly not covered by data regions, and logs and cached content are excluded.
- Direct messages between users in different regions are stored in both regions.
- Users on unsupported services or editions, such as Education Fundamentals, are not covered.
- In rare cases, such as natural disasters, users outside the selected region may lose access to data.
Privacy and admin notes
- The data covered for Workspace Studio is user-created flows, custom skills, step configurations and run history. Prompts and responses for the Gemini app and Gemini in Google Workspace are listed as separate covered data, at rest under all versions and in processing only on Enterprise and Assured Controls Data Regions.
- This page does not describe whether Studio data is used to train models; Google's pages above do not address it, so check the Gemini and Workspace privacy documentation for that.
- With any region other than No preference, the user-reported phishing alert may not appear in the Alert Center, according to Google. Workarounds named there are the security investigation tool (Gmail messages log) or a custom activity rule.
- Data Regions covers storage and processing location only. It is not a replacement for access controls, retention or compliance review.
- For the related Gemini controls, see Gemini in Google Workspace: plans, pricing and what is included and Google Gemini Agent in Workspace: plan and admin controls.
See also
- Do Small Businesses Need Google Workspace Backup? What Google Keeps and Doesn't
- Govern Copilot Studio Agents with Data Policies and an Environment Strategy
- Google Vids Assets: Reuse Your Media in AI Video Generation
What we checked
- Opened the Google Workspace Updates announcement on 2026-11-22 (IST). It confirmed the November 20, 2026 announcement date, the November 10, 2026 rollout start, the edition list, the 15-day visibility window and the blocked features.
- Opened the Workspace admin page "Set up advanced settings for data regions" on 2026-11-22. It confirmed the Menu > Data > Compliance > Data regions > Advanced settings path and the two option labels. It lists a shorter edition set than the announcement, noted above.
- Opened "Choose a geographic location for your data" (support.google.com/a/answer/14310028, which redirects to knowledge.workspace.google.com) on 2026-11-22 for the storage and processing steps, privileges and warnings.
- Opened "Data covered by data regions" (support.google.com/a/answer/14313033, redirected) on 2026-11-22. It confirmed the Workspace Studio covered data and the Gemini Notebook exclusion.
- Cross-checked the blocked Studio features between the announcement and the advanced-settings page; both agree on AI steps, Drive, Forms, Tasks and webhooks.
- Not tested on a live Workspace tenant; the rollout may not have reached every domain on 2026-11-22, and steps follow Google's documentation as of that date.
Last tested: 2026-11-22
Comments
Questions and tips are welcome. Comments are checked by the EpiFive team before they appear; please do not share passwords, phone numbers or other private details.