Okta's Profile Editor lets you add start date, hire date, and termination date as profile attributes and map them to 15Five using the SCIM extension namespace. Once mapped, these values sync automatically when Okta pushes user data to 15Five.
Before You Begin
Understand what each attribute controls in 15Five:
- Start date — the date an employee gains access to 15Five. Add this value before assigning the employee to the 15Five app in Okta. If the employee is assigned first, they receive a welcome email immediately regardless of start date.
- Hire date — the date the employee began at the company. Used in engagement surveys to populate tenure-based system groups.
- Termination date — the date an employee departed. Used in the HR Outcomes Dashboard to measure regrettable turnover.
SCIM provisioning must already be enabled and connected between 15Five and Okta.
Steps
- Open your Okta instance and navigate to the 15Five application configuration.
- Click the Provisioning tab.
- Click Go to Profile Editor.
- Click Add Attribute.
- Enter the Display Name for the attribute you are adding:
- Start Date, Hire Date, or Termination Date
- Enter the Variable Name:
- startDate, hireDate, or terminationDate
- Enter the following in the External namespace field:
urn:ietf:params:scim:schemas:extension:15Five:2.0:User
- Check User personal under Scope.
- Leave all other settings at their defaults.
- Click Save.
- Click Mappings.
- Click Okta User to 15Five.
- Select the Okta User field to map to the start, hire, or termination date attribute.
- If the desired field does not exist on the Okta User profile, create it as a custom attribute in Okta first.
- Click Save Mappings.
- Repeat steps 4–15 for each additional date attribute you want to sync.
Expected SCIM Payload Formats
POST / PUT payload example:
json "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:User", "urn:ietf:params:scim:schemas:extension:15Five:2.0:User" ], "urn:ietf:params:scim:schemas:extension:15Five:2.0:User": { "startDate": "12/15/2019" } `
PATCH payload example:
`json { "schemas": ["urn:ietf:params:scim:api:messages:2.0:PatchOp"], "Operations": [ { "op": "Replace", "path": "urn:ietf:params:scim:schemas:extension:15Five:2.0:User", "value": "12/15/2019" } ] } `
If Something Goes Wrong
| Issue | Check | Fix |
|---|---|---|
| Date attribute does not appear in 15Five after sync | Confirm the external namespace matches exactly: urn:ietf:params:scim:schemas:extension:15Five:2.0:User
|
Correct the namespace in Okta Profile Editor and re-save the attribute |
| Employee received a welcome email before their start date | Check whether the employee was assigned to the 15Five app before the start date attribute was saved | Remove and re-assign the employee after adding the start date attribute |
| Mapping field shows no available Okta User fields for the date | The Okta User profile lacks a corresponding date attribute | Create the custom date attribute on the Okta User profile, then return to Mappings |
| Changes are not pushing to 15Five | SCIM sync may not have triggered | Perform a force sync from Okta; if unresolved, contact 15Five Support |
Not Covered Here
This article does not cover syncing custom (non-date) attributes via SCIM — see the article on syncing custom attributes with Okta SCIM.