https://communities.sas.com/t5/Administration-and-Deployment/Restricting-Job-Scheduling-Access-in-SAS-Viya/m-p/988751#M30822 Rather than modifying the existing rules granting access you should disable them and create new ones granting the access you want, as the default rules are bootstrapped when the services start, so restarting of services would overwrite your changes.<BR /><BR />The ability to actually schedule a job for future execution is driven by create permission on the /scheduler/jobs object URI, but this would not impact the ability to run a job "now" (/jobExecution/jobRequests/&lt;job_request_id&gt;/jobs, /jobExecution/jobs) or create a job (/jobExecution/jobRequests) or flow (/jobFlowScheduling/flows). Updating a flow's schedule is controlled with Update permission on on the flow /jobFlowScheduling/flows/&lt;flow_id&gt;, but pushing that schedule is done with a call to /jobFlowScheduling/flows/&lt;flow_id&gt;/scheduled, and that call would fail if you already blocked permission to /scheduler/jobs, though this could result in the flow having a schedule defined that is not reflected in scheduler. Wed, 27 May 2026 17:34:45 GMT gwootton 2026-05-27T17:34:45Z https://communities.sas.com/t5/Administration-and-Deployment/Restricting-Job-Scheduling-Access-in-SAS-Viya/m-p/988676#M30821 <P>Hello,</P> <P>&nbsp;</P> <P>We have a requirement in our SAS Viya environment where only a limited set of groups ( mainly SAS administrator ) should be able to schedule jobs through SAS Studio or SAS Environment Manager.</P> <P>&nbsp;</P> <P>I tried modifying the authorization rules in SAS Environment Manager for the /scheduler and /SASjobexecution object URIs. Instead of granting permissions to the Authenticated Users group, I granted permissions only to the SAS Administrators group. However, non SAS Admin users are still able to schedule jobs through SAS Studio.</P> <P>&nbsp;</P> <P>Could you please let me know the complete list of object URIs that need to be restricted to control job scheduling access for specific groups?</P> <P>&nbsp;</P> <P>Thanks in advance.</P> Tue, 26 May 2026 19:22:02 GMT https://communities.sas.com/t5/Administration-and-Deployment/Restricting-Job-Scheduling-Access-in-SAS-Viya/m-p/988676#M30821 freshstarter 2026-05-26T19:22:02Z https://communities.sas.com/t5/Administration-and-Deployment/Restricting-Job-Scheduling-Access-in-SAS-Viya/m-p/988751#M30822 Rather than modifying the existing rules granting access you should disable them and create new ones granting the access you want, as the default rules are bootstrapped when the services start, so restarting of services would overwrite your changes.<BR /><BR />The ability to actually schedule a job for future execution is driven by create permission on the /scheduler/jobs object URI, but this would not impact the ability to run a job "now" (/jobExecution/jobRequests/&lt;job_request_id&gt;/jobs, /jobExecution/jobs) or create a job (/jobExecution/jobRequests) or flow (/jobFlowScheduling/flows). Updating a flow's schedule is controlled with Update permission on on the flow /jobFlowScheduling/flows/&lt;flow_id&gt;, but pushing that schedule is done with a call to /jobFlowScheduling/flows/&lt;flow_id&gt;/scheduled, and that call would fail if you already blocked permission to /scheduler/jobs, though this could result in the flow having a schedule defined that is not reflected in scheduler. Wed, 27 May 2026 17:34:45 GMT https://communities.sas.com/t5/Administration-and-Deployment/Restricting-Job-Scheduling-Access-in-SAS-Viya/m-p/988751#M30822 gwootton 2026-05-27T17:34:45Z