Hello @ShoichiroK.00155 (LAC Co., Ltd)​ Thank you for posting on our Community page!

The core issue is indeed the difference between an Okta-sourced user and a Directory-sourced user.

Here is the breakdown of why this behavior is happening and exactly how to resolve it for your Okta-sourced users.

The difference in behavior comes down to how Okta handles a user's Source of Truth (Master) when evaluating attribute mappings set to "Inherit from profile source".

• Case 1 (AD-Sourced User) - Success: Because the user was imported from Active Directory, they are an externally sourced user. When Okta sees an externally sourced user, it respects the global Profile Source Priority list you established (1. CSV, 2. AD). Because CSV outranks AD, Okta successfully pulls the "Title" attribute from the CSV Directory.
• Case 2 (Okta-Sourced User) - Failure: Because the user was created directly in Okta, they are an Okta-sourced user. For these users, Okta itself is the ultimate source of truth. When an attribute is set to "Inherit from profile source", an Okta-sourced user inherently looks to Okta as their master, effectively bypassing and ignoring external Profile Source priorities for that attribute. Even if the CSV Directory is linked later, Okta will not let the CSV overwrite the Okta profile unless explicitly told to do so.

How to fix Case 2

To force Okta to prioritize the CSV Directory's "Title" attribute for Okta-sourced users, you need to use Attribute-Level Sourcing. This allows you to override the user's master for one specific attribute without changing how the rest of their profile is managed.

Here are the exact settings required to resolve Case 2:

Step 1: Configure Attribute-Level Sourcing

1. In the Okta Admin Console, navigate to Directory > Profile Editor.
2. Click on Okta in the left menu (or search for the default Okta User profile) and click Profile.
3. Scroll down to find your Title attribute and click the Information (i) icon next to it.
4. In the attribute settings window, scroll down to the Source priority section.
5. Change the selection from Inherit from profile source to Override profile source.
6. A list of your integrated applications and directories will appear. Click Add Source if the CSV Directory is not already listed.
7. Drag and drop the CSV Directory to the absolute top of this list (Priority 1).
8. Click Save Attribute.

Step 2: Ensure "Update" Mapping is Enabled You must also ensure that Okta is allowed to continuously update this mapping, not just set it upon initial creation.

1. Still in the Profile Editor, go back to the main list and find your CSV Directory profile.
2. Click Mappings and select the CSV Directory to Okta User tab.
3. Locate the mapping for the Title attribute.
4. On the right side of the mapping, ensure the green arrow is active and the setting is set to Apply mapping on user create and update (the icon with two arrows).
5. If it is set to "Apply mapping on user create only" (single arrow), click it to change it.
6. Click Save Mappings.

Step 3: Trigger a Sync To apply these new rules to existing users immediately:

1. Go to Directory > Directory Integrations (or wherever your CSV integration is managed).
2. Run a full Import from the CSV Directory to force Okta to re-evaluate the mappings.

Once this sync completes, your Okta-sourced users (Case 2) will have their Okta mastery overridden exclusively for the "Title" attribute, and the value of "Manager" will successfully populate from the CSV Directory.

Thank you for reaching out to our Community and have a great day!

--

Help others in the community by liking or hitting Select as Best if this response helped you.