FaSailPoint logo

Identity and access management

Factorial to SailPoint integration: Factorial as the HR source for SailPoint Identity Security Cloud

With an integration between Factorial and SailPoint, SailPoint knows every new hire, contract change and termination from Factorial, so roles and access follow automatically and lapse after departure. KoppelHet delivers the employees per legal entity as an authoritative source, with job title and team as they apply on the effective date.

What the integration does

Organisations that use Factorial as their HR system and SailPoint for access governance often still work with lists. Without an integration HR exports lists of new colleagues and leavers, and revoking access lags behind the end date.

  1. HR records a new hire in Factorial; Factorial reports it as a new hire for the right entity.
  2. KoppelHet fetches the employee and their contract version and fills the work email following the naming rule.
  3. KoppelHet delivers the employee to the SailPoint source and starts the aggregation right away.
  4. A new contract version only goes to SailPoint on the effective date, so the role changes then.
  5. After the end date of a termination the identity becomes inactive and access lapses.
Factorial → KoppelHet → SailPointSOURCEFactorialFactorialTARGETSailPointKoppelHetmapping · logging · monitoringFactorial → KoppelHet → SailPointSOURCEFactorialFactorialTARGETSailPointKoppelHetmapping · logging · monitoring
Out: Identity with Factorial ID, name and work email · Job title and team from the current contract version · Legal entity and manager · Start and end date for the lifecycle state

What to watch for with Factorial and SailPoint

  • KoppelHet delivers to a standard SailPoint source, so the SailPoint team only manages the schema and the identity profile. SailPoint does not support custom connectors; their maintenance would fall to your team.
  • Factorial reports new hires, contract changes and terminations as separate types and can filter by legal entity. KoppelHet starts a delivery to SailPoint straight after a termination, while an ordinary contract change can go with the next run.
  • Job title and team are in Factorial in contract versions with an effective date. Roles in SailPoint that rely on team or job title only change when KoppelHet delivers the new version on that date, so an employee does not hold the rights of two teams for weeks.
  • Factorial is often used for several countries and legal entities. KoppelHet delivers the entity as a separate attribute, so SailPoint can limit roles and certifications per entity, for example to the finance system of one country.
  • Factorial switches off a webhook subscription after twenty failed attempts in 48 hours. KoppelHet monitors that and delivers all employees every night, so SailPoint knows about a missed termination by the next morning at the latest.
  • Factorial puts the API version with a date in the address. A failed or partial read run must never land in SailPoint as employees leaving. KoppelHet only forwards a file when the run fully succeeded, and tests a new version in Factorial's demo environment first.
  • SailPoint requires a work email for every identity, and a new colleague often does not have one in Factorial yet. KoppelHet fills the address following the naming rule per entity, so SailPoint already knows the identity as a pre-hire and the account is ready 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

Does this work with several legal entities?

Yes. The entity goes along as an attribute, and each entity can have its own naming rule.

What rights does KoppelHet get in SailPoint?

Only the rights to update this one source, no administrative rights over the whole environment.

Technical details for IT

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

  • KoppelHet reads Factorial through the Factorial API (version with a date in the path) with OAuth 2.0 - employee updates (new hires, contract changes, terminations) filtered on legal_entities_ids, employees, contract versions, teams and legal entities. Webhook subscriptions with up to twenty attempts in 48 hours, then disabled.
  • SailPoint Identity Security Cloud gets a Delimited File source as authoritative source; KoppelHet sends the CSV through the import-accounts API, which starts the aggregation right away. Required attributes uid, email and lastname; lifecycle states prehire, active and inactive through a transform on startDate and endDate.

Which fields are transferred

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

Field in FactorialField in SailPointNotes
Employee iduidKey of the identity
first_namefirstname
last_namelastname
Werkadres of naamgevingsregelemail
Functie (contract version)title
Teamdepartment
Legal entitycompany
Managermanager
Startdatum en einddatumstartDate 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.