Scoped Application Best Practice in ServiceNow Human Resources HRSD Applications

[Justin Little]

I am looking for best practice guidance. I am utilizing ServiceNow HR Lifecycle Events for a large project. Should all my customizations (integrations, flows, business rules, fields, etc.) be in a new scoped application? Or should I use the existing out-of-the-box (OOTB) HR Scoped App "Human Resources - Lifecycle Events" and just create update sets there? 

My understanding is ServiceNow wants customers to be creating scoped apps, I just don't know if we should make customizations within their OOTB scoped apps or create our own scoped apps for those customizations. Having scoped apps would be an advantage for this because I can easily package it up and move to different instances.

[Tanushree Maiti]

Hi @Justin Little ,

I'll suggest keeping your HR Services Events  within the OOB Human Resources Lifecycle Event scope when they relate to events like onboarding, offboarding, or promotions.

If you need to interact with functionality outside that scope, you can enable it through the cross-scope Privilege (Application Restricted Caller Access) module.

• Add/update fields, business rules, and Flow Designer logic as needed
• You would have versioning on your hand. What you have customized, you can check.

You should create a separate scoped app only when:

• You’re building completely custom functionality not tied to Lifecycle Events
• You need strict separation (e.g., reusable platform utilities, shared integrations)
• You want to isolate complex integrations or custom frameworks