1 of 1 people found this helpful
Sure – grant the roles whatever permissions are required in the role’s auth list and on the particular objects.
Thanks for the response, Bill.
I believe I have setup the ACL Policies and Roles with the appropriate permissions...still the other team member cannot even see the job running in their Tasks in Progress view.
For example, we have the 'DB Cleanup' job, being an NSH script job, created by me in the BLAdmins role and has an execution override to run as BLAdmin/BLAdmins.
I have object level permissions on that 'DB Cleanup' job, via 2 ACL Policies (1 for BLAdmins, 1 for Others) and there are no Access Control List direct grants of any kind...the 'BLAdmins' Policy has NSHScriptJob.* and the 'Others' Policy has NSHScriptJob.Cancel, NSHScriptJob.Execute, NSHScriptJob.ExecutionTaskOverride, NSHScriptJob.PauseResumeExecution and NSHScriptJob.Read.
And, for the user level roles that they each login with, the grants match the above as well, respectively.
And at last test, the user logging in with the 'Others' role had no visibility to see the running 'DB Cleanup' job.
Am I overlooking something in my setup?
I am not 100% sure what happened since the last test, as no changes were made to the Policies or Roles...it seems to be working for that other role now when I switch myself into it though.
I will follow-up with the other user and see if they are getting the same result since it does look like they should be able to view/monitor/cancel the running jobs I have those permissions applied to.
Thanks again for the quick reply,