3810897 - Restrict Job Requisition visibility for users with specific Job Code - SAP SuccessFactors Recruiting

• Need to restrict job requisition visibility so that users with specific Job Code cannot view job requisitions.
• Multiple users currently have visibility of job requisitions and must be restricted.
• Confirmation whether restriction can be implemented via Recruiting Groups, target population, requisition field permissions, or another supported configuration.

SAP SuccessFactors Recruiting Management 

1. Log in as a user with any Job Code.
2. Navigate to the Job Requisitions page.
3. Observe that job requisitions are visible in the Job Summary or search results.

• Users can see job requisitions because:
• They were assigned as operators or operator team members on those requisitions, or
• They were approvers during pre-approved status, and
• No configuration exists that excludes Job Code via Recruiting Groups, Role-Based Permission (RBP) target population, or Job Requisition Data Model (JRDM) field/operator permissions.

The recommended approach combines Recruiting Groups, Target Population configuration, and Requisition Operator/Field Permissions within the Job Requisition Data Model (JRDM). These three permission layers are executed in sequence, and if any one layer fails, subsequent layers are not evaluated.

1. Create a Recruiting Group that excludes that particular Job Code
   - Go to Admin Center → Managing Recruiting → Manage Recruiting Groups.
   - Create or edit a group; in People Pools, use Job Code as a criterion and exclude Job Code.
   - Use this group to limit who can be selected into operator/operator team fields for requisitions in the JRDM.
   Note: Recruiting Groups restrict selection into operator fields and apply to new requisitions after the template change; existing requisitions are not retroactively affected.
2. Adjust RBP target population to exclude Requisitions
   - Go to Admin Center → Manage Permission Roles and open the role(s) assigned to users with Job Code(the one you need to restrict)
   - In Assignments → Define target population, scope out requisitions (for example by department, division, or requisition-type attributes that identify HR).
   - Target population is a key layer evaluated for requisition access and prevents viewing even if template-level permissions exist.
3. Update JRDM operator and field permissions for HR templates
   - In the Job requisition template (JRDM), review role permissions (for example O, G, R, T, S, Q, W) per status.
   - Remove read/write permissions for roles assigned to users with Job Code(the one you need to restrict) for HR templates.
   - Reference the Recruiting Group from step 1 in and definitions to limit who can be selected.
   - Ensure these users are not assigned as operators for HR requisitions.
4. Validate the outcome
   - Impersonate impacted users and confirm selected requisitions are no longer visible while the other requisitions remain accessible.
   - Confirm visibility aligns with: a user sees a requisition only if they were a direct approver during pre-approval or are assigned as an            operator/operator team member.
5. Considerations
   - The permission layers (JRDM permissions, operator assignment/team recruiting, RBP target population) are evaluated in sequence; if any layer denies access, later layers are not evaluated.
   - Plan for existing requisitions separately if needed (for example, remove operator/team assignments that include the excluded users).

• Refer to: 3061958 - When does a job requisition becomes visible or accessible to a user? - Recruiting Management
• Refer to: 2291548 - Working with Recruiting Groups in SuccessFactors Recruiting
• Refer to: 2082005 - Team Recruiting functionality - Recruiting Management
• Refer to: Permissions for Requisition | Help Portal
• Refer to: Recruiting roles and permissions | Help Portal

job requisition visibility, requisitions, Recruiting Groups, target population, RBP, JRDM, operator roles, operatorTeam, permissions for requisition, team recruiting, exclude job code, manage recruiting groups, manage permission roles, recruiting access, data confidentiality , KBA , LOD-SF-RCM-JOB , Job Postings & Requisitions , Problem