Release Notes
Simplified Governance for Custom Agents and Workflows
Use custom agents and workflows as soon as you save them, with admin approval applied only at the sharing levels your firm chooses.
Important: This feature is rolling out in phases from October 14 through October 28, 2026. If you have questions about when this update will land in your workspace, contact your Customer Success Manager.
What's New
We’ve introduced a simplified model for how custom agents and workflows are governed in workspaces.
Approval is no longer required to create or run your own agents and workflows. New agents and workflows are ready to use as soon as you save them. If you want to edit an agent that is already live, you can save a new draft to make edits and test changes without affecting the live version.
Agent and workflow approvals now apply when you share them. By default, sharing with the entire workspace requires Agent Builder admin approval, while sharing with individual users does not. Admins can choose to require approval on all shares or workspace shares, or turn off requiring approvals.
Approval Defaults by Sharing Level
The table below outlines the default types of approval for custom agents and workflows when they’re shared in your workspace at different levels.
Sharing Level | Default | Admin Configurable? |
|---|---|---|
Whole workspace | Agent Builder admin approval required | Yes |
Specific individuals | Approval not required | Yes, can require approval |
Internal space | Approval not required | No, follows default Spaces behavior |
External space | Approval required from the space admin | No, follows default Spaces behavior |
Important: Shares made by an Agent Builder admin apply immediately and don't create an approval request for other Agent Builders.
For more on managing agents across your workspace, refer to Managing Agents.
Why It Matters
Under the previous drafting, publishing, and approval process, it could be difficult to tell whether an agent or workflow was a draft, published, or shared. Each new resource also waited on admin approval before anyone could use it.
Moving approval to the sharing step removes that wait for individual use. Agent admins can then focus their review on resources reaching wider groups, at the levels your organization chooses.
How to Use
Configure Sharing Approvals (Workspace Admins)
- Go to Command Center → Configurations → Sharing.
- In the Agents and Workflows sections, you can adjust the following options:
- Require admin approval for all shares
- Require admin approval for workspace shares
- When both toggles are off, sharing doesn't require approval.
The new rules apply to share requests made after you save.
- Go to Command Center → Users & permissions → Collaboration.
- Open Requests. If you manage only agent and workflow approvals, the page opens directly to Requests. If you also manage external collaboration requests, select Requests at the top right.
- Review the pending request, then select Accept or Deny.
For more on managing agents across your workspace, refer to Managing Agents.
Notes & Limitations
- Users who receive a direct share are notified. Sharing with the whole workspace doesn't send a workspace-wide notification.
- Agent Builder admins can receive an email and an in-app notification when a share needs approval, and the requester is notified when the request is approved or denied.
- Share requests go to every admin who can approve that request type:
- Workspace and individual shares: Agent Builder admins
- External space shares: The space’s admins
FAQs
Q: What happens to my existing agents and workflows?
Published agents and workflows don't change. Drafts of agents and workflows that are not shared, or shared with specific individuals or groups only, are saved and ready to use by recipients in the Library or Agents tabs. Pending publish and re-publish requests are cleared, since editing a shared agent or workflow no longer requires approval.
Q: What happens to a draft that was shared with the whole workspace?
Workspace access to that draft is removed, and the owner is notified that it needs to be re-shared. Re-sharing with the whole workspace follows your workspace's approval settings.