Skip to main content
sarthak
Employee
February 20, 2024
7.0 Duplicate

Sharing & Permissions (Agent Studio RBAC)

Related products:Agent Studio
  • February 20, 2024
  • 15 replies
  • 583 views

 

What problem does this solve?

Today every developer can see, edit, and publish every asset in your Agent Studio org. That forces teams to cap developer access to a small trusted group, blocking expansion into sensitive domains like HR, finance, and procurement. RBAC gives you fine-grained control over who can view, edit, and run each asset, so you can safely scale.

What's included:

  • Folders: Public (org-wide), Personal (drafts), and admin-created custom folders (e.g., "HR Integrations"). Assets inherit folder permissions automatically.
  • Four roles: Manager, Developer, Operator, Viewer, assignable per user per folder or asset.
  • Dependency enforcement: Running an asset requires Use permission on its full chain, including every action and connector it calls. 
  • Boundary states: When blocked, the UI names exactly what's missing and surfaces a "Contact owner" prompt.

How to get access

This feature is in Controlled Availability for a curated set of design partners. 

Key limitations in this release: no group-based permissions (individual users only), flat folder structure only, no bulk admin actions, and MCP Servers are outside RBAC scope.

Docs: linked here

 

 

15 replies

Ajay Merchia
Community Manager
February 20, 2024
1. New2. On Roadmap
sarthak
sarthakAuthor
Employee
April 18, 2024

Due to other upvoted items (namely connector editing and Creator Studio use case templates), we will be pushing our estimate of sharing privileges to later in 2024

Known Participant
April 18, 2024

Connector editing and use case templates would be more valuable to my team today. In the future I can see better access control by user or group to be a challenge to scaling out development.

Participating Frequently
June 18, 2024

this would be a good control for the use case. eagerly waiting when will it be released. It would be good also if we can put controls on who can published the use case in production

Lucas Rollo
Community Manager
August 20, 2024

Hey Folks! We are focusing on getting Plugins Workspace (Native Workflows), Import/Export, & Connector Editing out on time. As a result, Plugin Sharing Permissions will be pushed out to H1 2025.

Ajay Merchia
Community Manager
February 28, 2025
The following idea has been merged into this idea:

All the votes have been transferred into this idea.
Known Participant
February 28, 2025

As we’re engaging more of our shared services teams like HR, Finance, Payroll, we’re seeing a greater need for this in the very near future. 

While our Moveworks team has the capacity to build creator studio use cases for other teams today I anticipate the appetite for new plugins to outpace my current team’s work capacity and our current domain expertise (IT). I’m really looking forward to being able to configure access to creator studio plugins/compound actions/actions to users/groups so we can properly govern use cases across the entire enterprise.

Please and thank you!

-Anthony

Participating Frequently
June 3, 2025

this would be a good control for the use case. eagerly waiting when will it be released. It would be good also if we can put controls on who can published the use case in production

is it on track for Q3 preview release?

Known Participant
June 3, 2025

this would be a good control for the use case. eagerly waiting when will it be released. It would be good also if we can put controls on who can published the use case in production

is it on track for Q3 preview release?

Any updates would be greatly appreciated by my team as well. 

Please and thank you, 
-Anthony

Ajay Merchia
Community Manager
August 12, 2025
The following idea has been merged into this idea:

All the votes have been transferred into this idea.