I’m encountering a persistent permission denied error when attempting to import jobs using the Job Import Tool with target population filters applied. The import works fine when I don’t specify a target population, but as soon as I add population filters to restrict which requisitions get imported, the process fails with error code RCM_PERMISSION_DENIED. I’ve verified my administrator permissions include full recruiting module access and job requisition management rights. The target population itself is configured correctly and works in other contexts like candidate searches. Has anyone dealt with this specific permission issue when combining job imports with population-based filtering? We’re on SF H2 2023 and need to implement this for our regional hiring managers who should only see jobs for their specific locations.
The issue is likely related to how target populations interact with job import permissions. Target populations in recruiting require specific permission scope that goes beyond standard admin rights. Check if your admin role has ‘Manage Target Population’ permission enabled specifically for the recruiting module.
Let me provide a comprehensive solution based on troubleshooting this issue across multiple implementations.
For target population configuration: The first critical check is ensuring your target population is properly scoped for recruiting operations. Navigate to Admin Center > Manage Target Populations and review your population definition. The population must be explicitly marked as available for ‘Recruiting’ module use - there’s a checkbox in the population configuration that enables cross-module usage. Without this, the import tool cannot properly evaluate the population criteria.
Regarding role-based permissions: Your administrator role requires a specific combination of permissions that aren’t immediately obvious. Beyond standard recruiting admin access, you need: (1) ‘Manage Job Requisitions’ with ‘All’ scope, (2) ‘Import Job Requisitions’ permission, (3) ‘Use Target Populations in Recruiting’ permission, and (4) ‘Override Target Population Restrictions’ permission. The last one is key - it allows the import process to evaluate populations without being constrained by the administrator’s own visibility rules.
For administrator permission scope: This is where most implementations fail. Go to Admin Center > Set User Permissions > Administrator Permissions. Find your admin user and verify that under the Recruiting section, the ‘Job Requisition’ permission scope is set to ‘All’ rather than ‘Assigned’ or ‘Custom’. If it’s set to anything other than ‘All’, the import will fail when the target population includes requisitions outside your assigned scope. This is true even if you created those requisitions yourself.
Regarding batch import validation: The Job Import Tool runs under a system context that inherits permissions from your user account but also requires specific batch processing permissions. In Provisioning > Company Settings, search for ‘allowBatchImportWithTargetPopulation’ and ensure it’s set to true. Additionally, verify that the ‘Batch Import User’ (usually integration@yourcompany) has the same recruiting permissions as your admin account.
One often-overlooked aspect is the target population filter logic itself. If your population uses dynamic date filters or complex boolean logic, the import validation can fail due to ambiguous criteria. Test your target population in the Job Requisition search interface first - if it returns results there, the import should work. If the search fails or returns unexpected results, the population logic needs refinement.
Finally, for regional implementations where hiring managers should only see location-specific jobs, consider using RBP (Role-Based Permissions) instead of target populations for the import scope. Configure separate import jobs for each region with location-based filters in the import file itself, rather than relying on target population filtering. This approach is more reliable and provides better audit trails for compliance purposes.
After implementing these changes, test with a small batch import first (5-10 jobs) before running full-scale imports. Monitor the import logs in Admin Center > Monitor Jobs for detailed error messages that can help identify any remaining permission gaps.
Good point about field-level permissions. I’ve reviewed the target population filter and it uses standard fields like Location and Department. My admin role has view access to both. Still getting the same error though.