The News, Explained
Google announced a new Collaboration steps admin setting for Workspace Studio on November 19, 2026. A flow is an automation connecting tasks in sequence. The setting determines whether it may send information to other people or change shared resources. Collaboration is allowed by default, preserving existing email behavior until an administrator chooses to restrict it. Source
If an administrator restricts flows to creator-only actions, Gmail drafts and emails or notifications addressed only to the creator remain allowed. Sending, replying to or forwarding email to any other recipient is blocked. Files have a related boundary: editing an unshared document or spreadsheet owned by the creator is allowed, while editing a file shared with others is blocked. The same general email or editing task can therefore produce different results depending on its recipients or sharing state. Source
The restriction does not hide steps in the editor. Users can still see them while creating or editing a flow, but a step that affects another person is blocked when it runs, with an error explaining that the administrator blocked the action. Existing flows are affected on their next run; users do not need to switch them off and on. Understanding whether a step can run requires looking at both the editor option and the applicable admin policy. Source
The scope has boundaries too. The setting applies only to Google Workspace steps, leaving flow starters and read-only steps unaffected. Third-party integrations, custom steps and webhooks have their own admin settings; webhooks connect services by exchanging requests. File move and copy steps check only the destination folder, so moving or copying a shared file into an unshared folder can remain allowed. Treating this one setting as a universal barrier to information movement would overstate its coverage. Source
Administrators need the Service Settings privilege and configure the control under Workspace Studio → Collaboration & approvals → Collaboration steps in the Admin console. Settings can differ for organizational units, often used for departments, or specific groups; group settings take precedence over organizational units. The help page says a setting change can take up to 24 hours to propagate. Permission to collaborate and a requirement for user approval on external-sharing steps are separate controls. Source Source
The announcement lists a gradual rollout of up to 15 days starting November 19 for both Rapid Release and Scheduled Release domains. Eligible editions include Business Starter, Standard and Plus; Enterprise Standard and Plus; and Education Fundamentals, Standard and Plus. Its add-on list names Google AI Pro for Education, Teaching and Learning, and AI Expanded Access. Feature rollout and propagation of an administrator’s changed setting are also different timelines. Source
OYOPICK’s Take
The useful distinction is between allowing automation overall and allowing actions that affect someone else. Preserving personal drafts or work in an unshared document while adjusting collaborative actions could help organizations start with smaller automations. With steps still visible in the editor but blocked at runtime, we think the experience needs to make the reason and applicable policy clear enough for users to distinguish a permission change from a malfunction.
For this control to be useful, people need to understand what a flow reads and who it writes to. Read-only steps, separate external-connection controls and destination-based move or copy checks explain why. We hope future interfaces make each step’s impact and required permissions easier to understand.