Introduction
The Kallidus Sapling platform helps HR and People Operations teams automate and streamline administrative tasks so they can focus on employee experience, retention, and creating an amazing culture for the most successful teams.
Okta allows you to provide secure identity management and single sign-on to any application, whether in the cloud, on-premises, or on a mobile device for your employees, partners, and customers.
With our Okta integration, you can:
-
Launch Kallidus Sapling from Okta's single sign-on (SSO) portal
-
Sign in to Sapling using Okta credentials/authentication
-
Sending user data changes from Kallidus Sapling to Okta
This article covers the following topics:
Overview
We can provision Okta accounts for new hires. Here is a breakdown of how this happens:
-
New Hire data imported into Sapling
-
People Operations starts the new hire onboarding process in Sapling
-
Sapling provisions the initial account in Okta (sends attributes to Okta)
-
IT sets-up up all connected systems of new hire accounts (including G-suite, slack, Jira/confluence, etc)
-
IT triggers email invitation to new hire for Okta
*Please note if the invite email is sent immediately, then the Okta account is created immediately.
If an invite email is scheduled, then the Okta account will be created while triggering the invite email.
How It Works
Setting up the Integration
*Important note*
For this walkthrough, we used the Sapling HR app. When enabling the integration, search for Sapling App and use that option. This will ensure you can successfully enable the integration.
Data Flow Overview
Integration Fields
When a Sapling Admin completes the onboarding flow, Sapling will set up the new hire account in Okta with the fields listed below. Please note that this integration only syncs data from Sapling to Okta.
Sapling Field Name |
Okta Field Name |
---|---|
First Name |
firstName |
Last Name |
lastName |
Company Email or Personal Email |
|
Personal Email |
secondEmail |
Title |
Title |
Preferred Name + Last Name OR First Name + Last Name |
displayName |
Preferred Name |
nickName |
Home Phone Number |
primaryPhone |
Company Email or Personal Email |
login |
Mobile Phone Number |
mobilePhone |
Employment Status |
userType |
manager_id |
managerId |
Manager First Name + Last Name |
manager |
Home Address Line 1 + Home Address Line 2 |
streetAddress |
Home Address City |
city |
Home Address State |
state |
Home Address Zip |
zipCode |
Sapling Field Name |
Okta Field Name |
Notes |
---|---|---|
Division |
division |
If company department value is Division |
Sapling Field Name |
Okta Field Name |
Notes |
---|---|---|
Department |
department |
If company department value is Department |
💡 Looking to do more?
FAQs
- Will Sapling users be linked to their existing Okta profiles?
- Yes, when the integration is enabled Sapling users will be matched to their Okta profiles overnight
- Can two Okta instances for two different companies hook up to one Sapling instance?
- No, we only support integrating with one Okta instance
- Can specific fields be excluded from syncing from Sapling to Okta?
- Currently, we cannot exclude any of the fields listed in the section above from syncing
- How often are data changes synced from Sapling to Okta?
- Data changes to the listed fields are always synced immediately as long as the Sapling user has been matched to their Okta profile
- Will offboarded users in Sapling have their Okta profiles de-provisioned?
- Currently, we do not de-provision user accounts in Okta
Comments
0 comments
Please sign in to leave a comment.