Best practices for creating a system user for "Run As" in Scheduled Jobs
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 05:54 AM
Hi everyone,
We currently have more than 170 Scheduled Jobs running in our instance that do not have the Run As field populated. We are looking to improve this setup by assigning a proper system user to these jobs.
Could you please share your recommendations or best practices for:
- Creating a dedicated system user account to be used in the Run As field?
- Permissions or roles that this user should have?
- Any security or audit considerations when using a system account for Scheduled Jobs?
Thanks in advance for your advice!
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I know this is an older thread, but I wanted to supplement its content with a SN KB that speaks to this question:
This document recommends using a Run-As user, and specified the cmdb_inst_admin role.