Hi Joseph
The roles you are likely pointing to in Evolve pertain more to form solutions than scripts.
A few things come to mind:
(1) we use SAP security to access the underlying data, so anyone who runs them will need permissions for the underlying tables. And if you use security objects like company or plant to filter what they can see, they can be applied to the query to only see the data they should see.
(2) if you have Studio Manager or Evolve, you can segregate queries by creating Apps and only giving permission to users who should be able to see, open and run the queries in each App.
(3) might try library or solution permissions - but I'm not 100% sure that will do the trick

stop inheritance and setup whoever should be able to see/run them - which would be good to set in a custom group and then assign the group name, so that you can do it at a group level.
Hope that helps.
Best Regards,
Sigrid
------------------------------
Sigrid Kok
*Precisely Software Inc.
------------------------------
Original Message:
Sent: 03-21-2025 08:56
From: Joseph Gosser
Subject: Lock down Studio Queries
How can I lock down published queries from general users? I have a library created for these queries and I changed the permissions for the library to only allow one group to Originate the processes. However, in my testing, I am able to go into Studio, find these published queries and run them even though I am not in the specific group. Does this mean any Studio User can run these queries? How can I lock them down to specific power users?
------------------------------
Joseph Gosser
Business Analyst
The Andersons Inc
OH
------------------------------