There are particular options in LSF that enable you to allow non-owners to trigger jobs... although the are still called 'Administrators'... Role Where defined Summary of permissions Normal user Any operating system user on LSF hosts. All users are automatically assigned this role. Normal users can view flow definitions, flows, calendars, and jobs that are owned by all users but can control only work items that they own. Process Manager administrator Users that are specified in JS_ADMINS in the file js.conf after the first one that is listed. Process Manager administrators have full control over all Process Manager items of all users. Process Manager administrators can view, control, and modify flow definitions, flows, calendars, and jobs on behalf of other users. Process Manager Control administrator Users that are specified in JS_CONTROL_ADMINS in the file js.conf. Process Manager Control administrators can view flow definitions, flows, calendars, and jobs that are owned by all users and can control flows and jobs on behalf of other users. Process Manager Group administrator Users that are specified as GROUP_ADMIN in LSF user groups in thelsb.users file when JS_ENABLE_GROUP_ADMIN=true in js.conf. Group administrators can view flow definitions, flows, and calendars owned by all users. Group administrators can control flows and jobs on behalf of users who are members of the same LSF user group. As an admin I for one like the Idea to only allow admin to schedule (Should have been tested in UAT prior to being released and scheduled in production so no need to test) however this has other issues like who monitors job and resolves issues if it failes etc
... View more