Skip to main content

Google Adds a Workspace Studio Setting to Stop Flows Emailing, Posting to Chat or Editing Shared Files

Google's new Collaboration steps setting lets Workspace admins stop Workspace Studio flows reaching other people or changing shared files. It is on by default, and restricting it breaks existing flows at their next run. Where it is and what it blocks.

KBY News Desk8 min read
Two male colleagues exchanging documents in a modern office setting.

Google has added an admin setting that lets Workspace administrators stop automations built in Workspace Studio from emailing other people, posting in Chat or editing shared files. According to Google’s announcement on 19 November, the setting is called “Collaboration steps”, it is switched on by default so nothing changes until you act, and it can be set for a whole domain, an organisational unit or a group. If you restrict it, a flow that tries to reach another person fails when it runs and its owner sees an error. That includes flows that already exist, which Google says are affected the next time they run, so restricting it can quietly break automations people rely on.

#What the setting does, in Google’s words

Everything here comes from two Google pages, and we attribute the details to Google throughout: the announcement on the Google Workspace Updates blog, dated 19 November 2026, and the Admin Help article “Manage collaboration steps and approvals for Studio flows”, which Google shows as last updated on 17 November 2026. We also read Google’s “Get started” guide for Workspace Studio administrators for background. All three were read on 20 November.

Workspace Studio, per that guide, lets people create “flows” that automate routine work across Workspace apps such as Gmail, Drive and Chat. It says people with access to Gemini can build flows by describing what they want, that flows can use steps with AI, and that flows can act on a user’s behalf: drafting emails, creating and updating files, creating tasks and more. Google’s own warning in the guide is that a badly configured flow could unintentionally edit or delete data or send excessive notifications.

The new setting addresses the sharing side of that. Google says you can allow flows to collaborate across your organisation, or restrict them to actions that only the flow’s creator can see. With sharing allowed, which is the default, flows can send emails, post in Chat and edit shared files. With the restriction on, they can still send notifications to the creator, create drafts and edit files the creator owns that are not shared.

#Where it is and who can change it

The Admin Help article gives the path: in the Admin console, go to Menu, then Apps, then Google Workspace, then Workspace Studio, then Collaboration & approvals, then Collaboration steps. It says you need the Service Settings administrator privilege. You can apply the choice to an organisational unit or a configuration group, and group settings override organisational units. The two options are:

  • “Flows can share information with other users and modify shared organization data, such as sending emails, posting in Chat, and editing files”, which Google marks as the default.
  • “Flows can only perform actions visible to the flow creator, such as sending notifications, creating drafts, and editing files they own.”

You then click Save, or Override for an organisational unit. To go back to the inherited value you click Inherit, or Unset for a group. Google says changes can take up to 24 hours but typically happen more quickly.

#What gets blocked, and what does not

The restriction is enforced when a step runs, not when a flow is built. Google says all steps stay visible and are not dimmed in the editor, and if a step tries to share with another user or change a shared resource, it is blocked and the user gets a message that the action was blocked by their administrator. There is no end-user setting for any of this. Google’s table lists what that means for each service:

  • Gmail: sending, replying to or forwarding to any other recipient is blocked. Notifications to the creator, drafts and label, star or read-status changes are allowed.
  • Chat: posting or replying in spaces, or messaging other users, is blocked. Notifications to the creator are allowed.
  • Calendar: creating events with guests or adding guests is blocked. Events without guests are allowed.
  • Drive, Docs and Sheets: editing files shared with others, and creating, moving or copying items into a shared folder, are blocked.
  • Gemini Notebooks (NotebookLM): adding sources to notebooks shared with other people is blocked, while asking any notebook is allowed because asking only reads data.

Two limits matter. First, the setting applies only to Google Workspace steps and does not affect flow starters or steps that only read data. Third-party integrations, custom steps and webhooks have their own admin settings. Second, Google states a gap in its own table: move and copy steps check only the destination folder, so a flow can still move or copy a shared file into a folder that is not shared.

The same page covers a separate control, user approval, which asks the person who owns a flow to approve certain steps before the flow continues. Google gives these defaults: “Sensitive steps”, meaning steps that share data externally, default to “Let user decide”; custom steps and third-party Connectors steps default to “Never”, because those features are off by default. Google adds a note that choosing “Let user decide” for sensitive steps currently behaves the same as “Always”, so users must manually approve every step that shares data externally, and it says an upcoming change will let users choose between approving manually and auto-approval.

#Rollout and editions

The announcement describes a gradual rollout of up to 15 days for feature visibility, starting on 19 November, for Rapid Release and Scheduled Release domains. It names Business Starter, Standard and Plus; Enterprise Standard and Plus; and Education Fundamentals, Standard and Plus, along with the Google AI Pro for Education, Teaching and Learning and AI Expanded Access add-ons. The Admin Help article lists the editions slightly differently, and does not mention the AI Expanded Access add-on, so check your own console for the setting rather than relying on either list.

#Our reading: the default is a decision, even if you do nothing

Because the setting is on by default, leaving it alone keeps today’s behaviour: anyone with Workspace Studio can build a flow that sends email to other people from their own account. We think that is the real decision here. Whether or not you touch the setting, you are choosing whether staff can create automations that send messages and edit shared files without a person pressing the button each time.

We would not restrict it organisation-wide on day one. The more sensible first step is to restrict it for the groups where an automated message or a changed shared file does the most damage, such as finance, HR and anyone who handles customer records, and leave it open for a pilot group that is building flows on purpose. Because Google enforces it at run time and applies it to existing flows on their next run, a restriction can break something a team already depends on, and the first sign will be a user’s error message, not a notice to you. The pages we read do not say how to list which flows use collaboration steps, so ask your pilot group before you switch it on elsewhere.

For the approval setting, our view is that the current behaviour, where sensitive steps always need a manual approval, is a safeguard you should keep in mind before Google’s promised change lets users auto-approve them. We would review the setting when that change arrives. The same question, who may use agent-like features and what can they do, is the one Microsoft has put to Microsoft 365 administrators this week; we cover that in our story on Microsoft’s Copilot access-requests setting.

#What to do

  1. Check whether Workspace Studio is on for you. Google’s guide says to check Service status under Workspace Studio in the Admin console, per organisational unit and group.
  2. Look at the current Collaboration steps value and write it down. Allow for the rollout: it may not have reached your domain yet.
  3. Decide where sharing should be blocked, starting with the most sensitive groups, and warn their owners that flows which email, post or edit for others will start to fail with an error.
  4. Review the approval settings for sensitive steps, custom steps and Connectors, and leave custom steps and Connectors off unless there is a reason.
  5. Know how to stop a flow. Google’s guide suggests keeping a child organisational unit with Studio turned off, so you can move a flow’s owner into it to stop their flows quickly.

If a provider runs your Google Workspace, send them this question, word for word: “Is Workspace Studio turned on for our domain, what is the Collaboration steps setting, and who can create flows?”

#What we do not know yet

  • Whether the setting has reached your domain. Google says the rollout takes up to 15 days.
  • How to list which existing flows use collaboration steps. The pages we read do not say.
  • When Google’s change to the “Let user decide” approval behaviour will arrive. It says only “upcoming”.

We will update this story if Google changes the dates or closes the move and copy gap.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01Google Workspace Updates, New admin setting to control collaboration steps in Workspace Studio flows, 19 November 2026workspaceupdates.googleblog.com
  2. 02Google Workspace Admin Help, Manage collaboration steps and approvals for Studio flows, last updated 17 November 2026knowledge.workspace.google.com
  3. 03Google Workspace Admin Help, Get started: Workspace Studio set up guide for adminsknowledge.workspace.google.com

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on Google Adds a Workspace Studio Setting to Stop Flows Emailing, Posting to Chat or Editing Shared Files. Comments are checked for spam and held for moderation before appearing.

Loading comments...

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.