In an Okta org with an Active Directory and Workday profile source, should the Title attribute map from Workday?

Mapping the Title attribute from Workday makes sense in an organization that utilizes Workday as its Human Resources Information System (HRIS). Workday serves as a primary source of employee information, including job titles, organizational roles, and other relevant attributes. By mapping the Title attribute from Workday, you ensure that users in the Okta environment have access to the most up-to-date and accurate information directly from the system where employee data is centrally managed.

This approach supports efficiency and accuracy in user management. Workday is specifically designed for handling employee data, while Active Directory primarily manages network resources. If an organization relies on Workday for HR functions, it is logical to pull the Title attribute from it.

Mapping the Title attribute solely from Active Directory could lead to discrepancies if the information in AD is not regularly updated to reflect changes in job titles that occur in Workday. In addition, mapping titles from Workday allows for streamlined user provisioning and better alignment of access with current roles, which can improve overall security and ensure compliance with identity governance.

Choosing to map the Title attribute from Workday aligns with best practices in identity management, leveraging specialized systems to maintain data integrity.

The other choices imply different strategies that may not align as closely with optimizing the use of the specific