Talentech logoSailPoint logo

Identity and access management

Talentech to SailPoint integration: PeopleCore as the authoritative HR source for SailPoint

With an integration between Talentech PeopleCore and SailPoint, SailPoint gets an identity for every employee from Talentech with position, department, location, legal entity, manager and lifecycle state, so roles move along with hiring, job changes and resignations. Talentech and SailPoint have no connector for each other; KoppelHet delivers PeopleCore in full every hour to a Delimited File source in SailPoint.

What the integration does

Organisations that use Talentech PeopleCore for HR and introduce SailPoint for roles and reviews only find provisioning to Entra ID at Talentech and no Talentech connector at SailPoint. The SailPoint team then relies on exports someone makes by hand.

  1. KoppelHet gets a client in Talentech's token service with only read scopes for employees, positions, contracts and resignation applications.
  2. The SailPoint team creates a Delimited File source as authoritative source, with an identity profile and lifecycle states.
  3. Every hour KoppelHet reads PeopleCore, combines employee, position and contract into one row and builds the full file.
  4. KoppelHet sends the file to the source through the API, after which SailPoint aggregates.
  5. A transform sets the identity to inactive after the chosen date from the resignation application.
Talentech → KoppelHet → SailPointSOURCETalentechTARGETSailPointKoppelHetmapping · logging · monitoringTalentech → KoppelHet → SailPointSOURCETalentechTARGETSailPointKoppelHetmapping · logging · monitoring
Out: Identity with Talentech ID, name and work email · Position with job title, department, location and legal entity · Manager from the superior position · Start date, last working day and employment end date

What to watch for with Talentech and SailPoint

  • Talentech only describes HR-driven provisioning to Entra ID, and Talentech's SCIM API is meant to put users into Talentech ID, not to read them out. SailPoint has no Talentech connector. KoppelHet therefore reads the PeopleCore API and delivers to a Delimited File source.
  • PeopleCore cannot query employees by change date. For an authoritative source in SailPoint that is no drawback, because it should get the full state. KoppelHet reads all employees every hour and delivers the complete file every run, so a missed run corrects itself.
  • On a job change Talentech closes the old contract and opens a new one on another position. SailPoint must see that as a move, not as a departure and new hire. KoppelHet keeps the Talentech ID as uid and only puts the new position details in the row, so SailPoint sees a mover event.
  • Department, location and legal entity hang on the position in PeopleCore and are stored there as IDs. KoppelHet looks up the names and delivers them as separate columns, so a role in SailPoint can, for example, cover all employees of one entity at one location.
  • SailPoint links a manager through manager correlation to an account in the same source. In PeopleCore the manager follows from the superior position, which can be vacant. KoppelHet puts the Talentech ID of the holder in the column, or of the position above, so approvals in SailPoint always land with a person.
  • A resignation application in PeopleCore has a last working day and an employment end date. KoppelHet delivers both, so the transform in SailPoint can choose; with garden leave, access then lapses after the last working day.
  • KoppelHet leaves profiles still in draft in PeopleCore out of the file. A completed profile with a future start date is included, so SailPoint sets the identity to pre-hire and assigns the roles on the start date.

This integration is also part of joiner, mover, leaver.

How we build and run it

  • The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
  • Every sync and every error is visible in the functional log; on an error your administrator is notified.
  • A change that cannot go through is not half-applied but queued for another attempt.
  • KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
  • After go-live we manage the integration and adjust it when your process changes.
  • The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.

Implementation, architecture and compliance

Implementation and price

This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.

A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Can Talentech not provision to SailPoint itself?

Talentech only names Entra ID as a target. Feel free to ask Talentech; KoppelHet builds the integration if there is nothing.

Does salary data go to SailPoint?

No. The client has no scope for salaries or national IDs.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Talentech PeopleCore API (api.talentech.io/peoplecore) with a JWT from the token service (client credentials) and read scopes only: GET /v1/Employees (isDrafted, businessContactInformation.businessEmail, positionId), /v1/Positions (jobTitle, departmentId, locationId, legalEntityId, superiorPositionId, isVacant), /v1/Contracts and /v1/EmployeeResignApplications (lastDayOfWork, employmentEndDate).
  • SailPoint Identity Security Cloud with a Delimited File source as authoritative source; delivery through the import-accounts API, which starts the aggregation. Required attributes uid, email and lastname; Manager Name through manager correlation; Lifecycle State through a transform on startDate, lastDay and endDate.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in TalentechField in SailPointNotes
employee id (Talentech)uidKey of the identity
Voornaamfirstname
Achternaamlastname
businessEmail of naamgevingsregelemail
jobTitle (positie)title
departmentId, locationId en legalEntityIddepartment, location en company
superiorPositionIdmanagerTalentech ID of the holder
Startdatum contractstartDate
lastDayOfWork en employmentEndDatelastDay en endDate

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.