How to find the best user account for 'Run as' in Scheduled Jobs/Reports?

[georgechen]

Hi folks, 

I need some advice on the best practices on Run as user for Scheduled Jobs/Reports in ServiceNow, hoping someone could advise!  Currently the organisation I am working for has an represent account who has admin role that can do everything including trigger events, generating reports, executing scripts, etc.  Security wise, this is not the best practice, it admin role is kind of overkill, however, when running the jobs as a non-admin users, it does not seem to work perfectly, e.g some reports might be missing certain columns, some records not updated properly down to ACL for example, 

As the reports and scheduled jobs involve a lot of efforts to going through each and to figure out which table access (read/write), I was wondering in ServiceNow was there any Best Practice to set up the Run as account not only to carry out the jobs but also meet the security practice?

Thanks in advice. 

George

[Chalan B L · Accepted solution]

Hello George, 1) if you keep Run as empty then it will take system administrator account automatically and runs the job 2) not recommended to use any user profile because if the user becomes inactive in the future then the job will never run 3) to run the schedule job role required is admin so use system administrator user as run by Mark the answer as correct if it helped you...!!! Regards, Chalan

[MayuriSurap]

Hello Chalan, Could you please explain how to change run as to System administrator as its read only field in scheduled job.

[Prateek kumar]

The system already has an OOB account with admin role named as System Administrator.

You can make use of this.

[charliesdev]

FYI  Had to include that "Run as" field when listing all Scheduled Jobs to see/change that value.