Custom attributes let you pass additional employee profile data from Okta into 15Five fields beyond the standard SCIM attribute set. When configured, Okta pushes the custom value to 15Five automatically on each sync.
Before You Begin
- SCIM must already be enabled in 15Five and connected to your Okta instance.
- You must have admin access to the Okta Profile Editor for the 15Five app.
Steps
- In Okta, open the 15Five application and navigate to the Provisioning tab.
- Click Go to Profile Editor.
- Click Add Attribute.
- Enter a Display Name for the custom attribute (for example,
Department Code). - Enter a Variable Name prefixed with
custom(for example,customdepartmentCode). - Enter the following in the External namespace field exactly as shown:
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, then click Okta User to 15Five.
- Locate your new custom attribute in the attribute list.
- Select the Okta user field you want to map as the source value.
- Click Save Mappings.
Okta will now send the custom attribute value to 15Five on each provisioning sync.
If Something Goes Wrong
| Issue | Check | Fix |
|---|---|---|
| Custom attribute does not appear in 15Five | Confirm the variable name uses the custom_ prefix exactly |
Edit the attribute in Profile Editor and correct the variable name |
| Attribute saves but value is empty in 15Five | Confirm the external namespace string matches exactly | Copy the namespace string directly from this article and re-enter it |
| Mapping field is not available in the Okta User profile | The source field may not exist as an Okta user attribute | Create the attribute on the Okta User profile before mapping |
| Changes not reflected after saving mappings | Okta may not have pushed an update since the mapping was saved | Trigger a manual profile update for a test user in Okta to force a sync |
Not Covered Here
This article does not cover syncing standard attributes (first name, email, manager, dates) or configuring custom attributes in IdPs other than Okta.