eRecruiter

Automatic transfer of hired candidates from eRecruiter

ATS / Requires Recruit module

Once a candidate gets the Hired status in eRecruiter, their employee profile is created in PeopleForce automatically: full name, email and employment start date. Recruitment stays in eRecruiter, and onboarding begins in PeopleForce.

Integration capabilities

Once the systems are connected, a hired candidate's data moves to PeopleForce the moment they get the Hired status, and HR starts onboarding on a ready profile.

Automatic employee profile creation

A candidate who has gone through the full hiring path to the Hired status appears in the PeopleForce employee directory as a new profile with full name and email. Position, department, employment type and documents are then completed in PeopleForce, with no retyping of recruitment data.

Start date from recruitment

The start date set in eRecruiter becomes the employment start date in the PeopleForce profile. On that day, the onboarding workflow with the new hire form begins, so onboarding starts on schedule with no manual date setting in the profile.

Choosing which recruitments are included

The scope is set in eRecruiter when generating the token: selected recruitments or all of them. In addition, every new recruitment has a PeopleForce integration checkbox, so the person running the recruitment decides on the transfer, and hires from recruitments with the box checked reach PeopleForce.

How it works

What data reaches PeopleForce

Data flows in one direction: from eRecruiter to PeopleForce, the moment a candidate gets the Hired status. Stages, ratings and candidate communication stay in eRecruiter, and from the hire date onward, the employee is managed in PeopleForce.

What is transferredDirectionWhenData
New employee
profile in the employee directory
eRecruiter PeopleForce
Hired status
full name, email
Employment start date
start date from recruitment
eRecruiter PeopleForce
together with the profile
start date as the employment start date

The profile is created with the core data from recruitment. Position, department, employment type, salary and documents are completed in PeopleForce manually or through the new hire form in the onboarding workflow, which starts on the employment start date.

Integration conditions

What you need to get started, where recruitment happens, and how the API key is set up.

Setup takes two tokens and the support team

The access token is generated in eRecruiter in the list of integration partners, for selected or all recruitments; the API key is created in PeopleForce under Settings → Security → API keys. Both go to the PeopleForce support team, which connects the accounts.

Recruitment happens in eRecruiter

Job ads, stages, ratings and candidate communication stay in eRecruiter. The PeopleForce integration checkbox in each recruitment decides whether its hires reach PeopleForce after getting the Hired status.

API key with full access and sensitive data kept off

A Company key gives the integration full read and write access to company data through the API. The four sensitive data toggles (people compensation, role compensation range, candidate expected compensation, candidate sensitive fields) are set to None by default and stay that way.

Frequently asked questions

What HR teams ask before launching the integration and after sending the tokens to support.

Step-by-step guide in the help center

When does a candidate appear in PeopleForce?

Can the integration be limited to selected recruitments?

What happens after the tokens are sent to support?

See how a candidate moves to PeopleForce

From the Hired status in eRecruiter to a ready employee profile and the first day of onboarding, using your own recruitment as the example.