Workday logoSaviynt logo

Identity and access management

Workday to Saviynt integration: Workday as the identity source in Saviynt, with Saviynt's connector

Saviynt has its own Workday connector that imports workers from Workday as identities in Saviynt Enterprise Identity Cloud, and can also manage accounts and access in Workday itself. With an integration between Workday and Saviynt, hire, job, department and departure in Workday therefore decide who gets which access; KoppelHet sets up the connector and covers where it falls short, such as workers with a future start date.

What the integration does

Organisations that use Workday as their HR system and Saviynt for identity governance have the Workday source set up during the Saviynt project. Afterwards it turns out that new employees only get an identity on their first day, that a departure sometimes only comes through at the next full import, and that the email address from Saviynt is not in Workday.

  1. In Workday we create an Integration System User with its own security group and only the rights the connector needs.
  2. In Saviynt we set up the Workday connector, with the employee number as username.
  3. For new workers with a future start date we set up a separate report or filter, so the identity exists before day one.
  4. Alongside the incremental import we schedule a full import, so changes and departures are picked up as well.
  5. The email address Saviynt creates is written back to Workday by the connector.
Workday → KoppelHet → SaviyntSOURCEWorkdayTARGETSaviyntKoppelHetmapping · logging · monitoringWorkday → KoppelHet → SaviyntSOURCEWorkdayTARGETSaviyntKoppelHetmapping · logging · monitoring
Out: Workers as users in Saviynt · Job, department, manager and location as attributes · Start date and end date · Work email back to Workday

What to watch for with Workday and Saviynt

  • Saviynt builds and maintains the Workday connector itself, under its own support and maintenance agreement. According to Saviynt all Workday integrations run through Workday's web services API; KoppelHet therefore builds no import of its own, but sets up that connector.
  • The connector does more than import. Saviynt also lists creating, changing, enabling and disabling accounts in Workday and adding or removing access. Using that lets Saviynt manage the Workday permissions themselves too; KoppelHet keeps that role out of scope at the start and lists it as an extension.
  • Saviynt advises putting the unique HR identifier on the username attribute. KoppelHet uses the Workday Employee_ID for that, and their own ID for contingent workers, so a move from external to internal does not create a second identity.
  • According to answers on the Saviynt forum, an incremental import on a Workday report only brings in new users. KoppelHet therefore also schedules a full import, so a job change or departure does not wait until someone starts it by hand.
  • Workday stores a hire with an effective date, and a standard report often only shows who is employed today. For workers starting in two weeks KoppelHet uses a report or filter on future effective dates, so their account is ready on the first day.
  • Saviynt describes in its knowledge base how a generated email address goes back to Workday. KoppelHet sets up that return path, so the work address in Workday matches the account, and gives the integration user in Workday write access only to work contact information.
  • From version 23.12 the connector supports OAuth for import and provisioning according to the Saviynt forum, alongside basic authentication. KoppelHet chooses OAuth with a refresh token, so a password policy in Workday does not stop the import.

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

Saviynt already has a Workday connector. Why KoppelHet?

The connector only works well when Workday reports, permissions and schedules are right. KoppelHet sets that up and monitors it afterwards.

Does a new employee get an account before the first day?

Yes, if the report also includes future effective dates. We set that up at the start.

Can Saviynt also manage the permissions in Workday itself?

According to Saviynt it can, with accounts and access in Workday. We keep that out of the first version.

Technical details for IT

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

  • Saviynt Workday connector (developed by Saviynt) through the Workday web services; operations according to Saviynt Exchange - Full User Import, Full Account Import, Full Access Import, Create, Update, Enable, Disable and Remove Account, Add and Remove Access, Change Password. Account mapping adjustable through ACCOUNT_IMPORT_MAPPING.
  • Workday: Integration System User with its own security group, reading through Get_Workers or a RaaS report, writing back the work address through the Maintain_Contact_Information web service. Authentication with OAuth 2.0 (API client with refresh token) or basic authentication.

Which fields are transferred

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

Field in WorkdayField in SaviyntNotes
Employee_IDusernamePrevents duplicate identities
Legal_Namefirstname, lastname
Business_Titletitle
Supervisory_Organizationdepartmentname
Manager Employee_IDmanager
Hire_Datestartdate
Termination_Dateenddate
Work email (terug)Email_Address in WorkdayGenerated by Saviynt

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.