Multiple users shared their struggles in effectively organizing script access, with one suggesting the use of DEX RBAC and the new platform tagging system to improve granularity. The ControlUp team will discuss this internally.
Read the entire ‘Improving Granularity in Script Access with DEX RBAC and Platform Tagging’ thread below:
Has anyone found a way to effectively organize script access? By design it seems you need to classify script by impact then assigned roles to certain script groups. It would be nice to have granular access to each scripts access controls. For example, field services and service desk associates may utilize many of the same scrips, but field services may have more control over a single device. Likewise Identity teams may use some scripts that other teams use but have more restricted client access. Just wondering how others organize script access? I can’t be the only one desiring more granularity in this area.
Would love to hear @member and @member feedback on this one
We will discuss this internally. I have heard this before. Our DEX RBAC system might not support the thing that I want now, but maybe with the new platform tagging system we can make it work.
Continue reading and comment on the thread ‘Improving Granularity in Script Access with DEX RBAC and Platform Tagging’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers