Designating Users as Resources in ServiceNow<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Executive Summary To enable resource management capabilities for users in ServiceNow, they must have the pps_resource role assigned. This article explains how to efficiently provision this role using group membership. The pps_resource Role In ServiceNow's Resource Management framework, a user becomes a "resource" - eligible for assignment to projects, tasks, and demands - only when they have the pps_resource role. Without this role, users won't appear in resource pools or be available for allocation through the Resource Management Workspace. Assigning the Role via Group Membership The recommended approach is to leverage ServiceNow's group-based role inheritance: Create or identify a group (e.g., "All Resources" or "Project Resources")Assign the pps_resource role to the groupAdd users to the group as members Result: All members of the group automatically inherit the pps_resource role, making them available as resources. When new employees join, simply adding them to the group provisions their resource capabilities instantly. Benefits: Scales easily to hundreds or thousands of usersSimplifies onboarding and offboardingProvides a single point of control for resource eligibilityAligns with ServiceNow best practices for role management A Note on Manual Assignment While it is technically possible to assign the pps_resource role directly to individual user records, this approach does not scale. Manual assignment is time-consuming, error-prone, and difficult to maintain as the organization grows. Group-based assignment should always be used instead.