Supported editions for this feature: Business Starter, Business Standard, and Business Plus; Enterprise Standard and Enterprise Plus; Education Fundamentals, Education Standard, Teaching and Learning add-on, and Education Plus. Supported add-ons for this feature: Google AI Pro for Education.
This feature is in limited preview.
Google Workspace custom starters and steps are created by developers in your organization or third parties. These starters and steps can help your users’ flows work better with your organization’s existing systems. However, users can add variables to custom starters and steps that could share your organization's data externally or with the custom starter or step developer (for example, in the contents of a Gmail or Chat message, a document in Drive, or event information from Calendar).
This page explains how you can control who can use both custom starters and steps and unpublished (test version) custom starters and steps and which custom starters and steps are available.
About unpublished custom starters and steps
Before custom starters and steps are published to the Google Workspace Marketplace, they are tested and installed from a test deployment. Any user that the Google Apps Script is shared with can also install the app's test version. Learn more about testing and debugging Workspace add-ons.
You can control whether your users can use unpublished custom starters and steps. By limiting access, you can prevent users from re-creating blocked starters or steps or using a test deployment to get around this setting.
Choose who can use and test custom starters and steps
You can allow your users to test custom starters and steps that haven't been published on the Google Workspace Marketplace. You can also limit your users to only those published starters and steps that you've allowed, or you can restrict the use of custom starters and steps completely. By limiting access, you can prevent users from recreating a blocked starter or step and using a test deployment to get around this setting.
Before custom starters and steps are published, they are tested and installed from the same test deployment. Any user that the Google Apps Script is shared with can also install the app's test version. Learn more about testing and debugging Workspace add-ons.
Before you begin: If needed, learn how to apply the setting to a department or group.
-
In the Google Admin console, go to Menu
Apps
Google Workspace
Workspace Studio.Requires having the Service Settings administrator privilege.
- Click Custom steps settings.
- (Optional) To apply the setting only to some users, at the side, select an
organizational unit (often used for departments) or configuration group
(advanced). Show me how
Group settings override organizational units. Learn more Choose an option:
- Off—The default setting. Flows can't use custom starters or steps. Any flows that used custom starters or steps previously won't work anymore.
On—Flows can use published custom starters and steps that you allow.
Check the Allow unpublished (test) custom steps box to let users test unpublished custom starters and steps and share them with others.
Note: Your data access settings apply to unpublished starters and steps, but you can't manage these in the Google Workspace Marketplace.
Click Save.
Manage availability of custom steps
When you allow custom starters and steps, you can manage which starters and steps are available to use in flows and what data they can access.
Custom starters and steps are installed through the Google Workspace Marketplace. You manage these just like any Google Workspace add-on that's published in Marketplace. You can: