Certain attributes may not reflect the expected value in the Okta User profile when imported from Workday. Reviewing the imported Workday AppUser profile, an Okta admin might find that the attribute does not reflect the expected value and instead shows "Overrides default value" below the field, indicating that the attribute source is set to Admin-managed instead of Default (mappings).

• Workday
• Provisioning
• Mappings
• Universal Directory
• Profile Sourcing

• The attribute source is set as Admin instead of following the default profile mapping.
• The profile source is other than Workday.
• If the attribute reflects properly in the AppUser profile but has not updated the mapped Okta User attribute, please see Users Not Updating from Profile Source to identify next steps.

The attribute source will need to be reset from Admin to Default. Resetting here simply means reverting the manual/overriding value to the configured mapping. This will not negatively change the mapping or the attribute.

Troubleshooting steps to complete first:

1. Try a Force Sync from Workday to Okta, as presented in How to Use the Force Sync Option documentation. 
2. Change the affected attribute (for example, street address) from inherit from profile source to Override profile source and set the appropriate priority. 
3. Validate the priority source of Workday.

If this is a single attribute, this may easily be done via the Okta Admin Console UI:

1. Navigate to the profile source integration in the Okta Admin console.
   • (This can be done from Directory > Profile Source > clicking the name of the integration or by navigating to Applications > Applications > search for the integration name).
2. Select the Assignments tab.
3. Search for the Okta User and click the edit pencil icon on the right side of the search result.
4. Locate the attribute and choose Reset as seen here:

5. Click Save.

If this must be done in bulk, please open a case with Okta support with the following:

• Reference or link this article along with the troubleshooting steps taken so far.
• Provide the full Okta Org URL or orgId where this is occurring.
  • for example, https://example.okta.com or https://example.oktapreview.com.
• Application ID (if there are multiple Workday instances in the tenant).
• The exact variable name of the affected Workday attribute.
  • Variable names can be found in the Okta Admin Dashboard under Directory > Profile Editor > Workday > under the column Variable Name.
• Any relevant screenshots illustrating this issue.
• Request Okta Support review if this scenario matches, and reset the attribute source from admin to default if appropriate.

Related References

• Attribute Value not Synced from Workday to Okta
• Workday Real-Time Sync
• Why Would Workday Email Writeback Not Getting Triggered Immediately Upon Okta New User Account Creation via Workday Import
• Users Not Updating from Profile Source