https://communities.sas.com/t5/Administration-and-Deployment/Security-Question-for-SAS-DI-4-2/m-p/248061#M4036 <P>Is there a way to allow someone to run jobs but not make changes to them. We want to allow and analys to run data loads but we don't want them to be able to alter the job or change the underlying SQL.</P> Thu, 04 Feb 2016 18:46:25 GMT Roc 2016-02-04T18:46:25Z https://communities.sas.com/t5/Administration-and-Deployment/Security-Question-for-SAS-DI-4-2/m-p/248061#M4036 <P>Is there a way to allow someone to run jobs but not make changes to them. We want to allow and analys to run data loads but we don't want them to be able to alter the job or change the underlying SQL.</P> Thu, 04 Feb 2016 18:46:25 GMT https://communities.sas.com/t5/Administration-and-Deployment/Security-Question-for-SAS-DI-4-2/m-p/248061#M4036 Roc 2016-02-04T18:46:25Z https://communities.sas.com/t5/Administration-and-Deployment/Security-Question-for-SAS-DI-4-2/m-p/248074#M4037 How do your analysts execute the code? You could deploy the jobs as stored processes if they are to be fired at will. <BR />The actual deplyed SAS code should be secured by OS authorization. <BR />The DI Studio jobs should be secured in Metadata (no access/RO). Thu, 04 Feb 2016 19:52:36 GMT https://communities.sas.com/t5/Administration-and-Deployment/Security-Question-for-SAS-DI-4-2/m-p/248074#M4037 LinusH 2016-02-04T19:52:36Z