Skip to main content
jbentahir
Known Participant
November 22, 2024
4. Future Consideration

Creator Studio role separation

Related products:Agent Studio
  • November 22, 2024
  • 3 replies
  • 21 views

I would like to be able to give access in Creator Studio to “Developers” who only have access to certain areas (Events and Queries) for example. They would be able to use creator studio only for those scenarios and not all of the capabilities. This would allow us to have “citizen developers” build their own use cases based on their skills. 

3 replies

Ajay Merchia
Community Manager
December 4, 2024

Hey ​@jbentahir -- interesting idea. As we move to Agentic Automation Engine, there is only going to be one area to build (Plugins).

I’m curious, why are you looking to make a “who’s enabled” into an “access control” problem? Are you looking to certify / verify that people know what they’re doing before they build?

Ajay Merchia
Community Manager
December 4, 2024
1. New4. Future Consideration
jbentahir
jbentahirAuthor
Known Participant
December 4, 2024

We would like to be able to give easier use cases over to the business themselves; however, many of these automation enablers, do not know how to use Yaml or Python for example. We would want to be able to give them access to only the areas they could utilize. Additionally, we would want to verify their use cases before going live. So we wouldn’t want them to be able to have their automations go live without review of our development team. 

Jennifer Bentahir