Internal Candidate Profiles created for Contingent Workers

[lauranovoa]

Hi Experts!

We have noticed for various customers that when Contingent Workers are hired in SuccessFactors, and internal candidate profile is automatically created "As if they were employees". We have not granted "Careers" permission to contingent workers as CWs are not supported in RCM and ONB.

This has resulted in various issues like the following:

• The Contingent Worker cannot apply with their personal email to a new permanent position if this is the email used when creating their Contingent Worker account.
• Integration with external ATS (e.g LiveHire) creates the application associated to the internal candidate profile of the contingent worker. Therefore, they cannot access the offer at offer status because they don't have internal career site access.
• Contingent worker recruiting processes cannot be included in reporting as they don't follow the recruit-to-hire process.

Has anyone have had issues with contingent workers and the RCM and ONB modules? What issues have you had? How have you overcome them?

Does anyone know if there is a way to control the automatic creation of internal candidate profiles for contingent workers?

Thanks so much for your help. More information about this issue will help many customers.

Laura Novoa.

[mjmitra]

Hi laura_novoa,

Depending on whether you have DPCS or not, here is the information on how candidate profiles are created.

Candidate Creation Scenarios

https://help.sap.com/docs/SAP_SUCCESSFACTORS_RECRUITING/8477193265ea4172a1dda118505ca631/b9ecc48ba46...

From the list available, I'm thinking your scenario probably match the no DPCS setup and the internal candidate profile is created when the following scenario is met.

• When, a Recruiter has searched for the Recruiting candidate and clicked on the candidate name (from the results).

This scenario instantaneously creates the internal candidate profile.

If this is the case, you have no way of preventing the creation of the profiles, unless the users do not search for the candidates (which is hard to control). Also, you cannot interfere with the provisioning jobs that manage these creations since that would most likely affect all the internal candidate profile creations on your system and not just for contingent workers.

Thank you,

Jubelle

[lauranovoa]

Hi Mary,

Thanks for looking into this. But to test that the internal candidate profiles were not being created under this scenario, we ran the following test:

1. Add contingent worker.

2. Run a candidate report using the contingent worker's first name as a filter.

3. Contingent worker candidate profile comes as one of the results of the report.

This demonstrates that the internal candidate profile is being created automatically.

[nlgro023]

Normally the internal employee to candidate shouldn't happen if contingent workers don't have access to internal careers (as they then cannot internal apply/go there, which are 2 of the triggers). I guess the main issue is that onboarding 2.0 doesn't support the contingent worker and that RCM doesn't exactly support a good flow of them either. Crossboarding hasn't been quite the solution for them either, instead the choice is often still made to have them as external applicants in onboarding and, when you try to move them to EC, just go for rehire (with new id).

[lauranovoa]

As per your comment: "Normally, the internal employee to candidate shouldn't happen if contingent workers don't have access to internal careers"

I don't think this is the case any longer. Contingent Workers don't have "Careers" permission and still candidate profiles are being created for them without searching them in the candidate Data Base directly.

This is the Test Scenario:

1. Add contingent worker.

2. Run a candidate report using the contingent worker's first name as a filter.

3. Contingent worker candidate profile comes as one of the results of the report.

[nlgro023]

My guess is that someone turned on a provisioning job then that converts employees to internals then. The benefit is that no one is left behind. The downside is that it knows no restriction. Perhaps worth it to have that checked and if that is scheduled, it may be a consideration not to use it going forward.