31% of Part II — the largest hands-on use case.
3 tasks · this deck covers task 2 of 3
↑ Application Setup OverviewOnce an app is connected, its fields and Okta's profile fields need to agree on what data means the same thing. That agreement is the attribute mapping — and it has a direction.
The Profile Editor lets you connect Okta user attributes to application attributes, making Okta either "the single source of truth for user data, or the recipient of user data."
Two directions exist: App to Okta (the app is the source, Okta receives) and Okta to App (Okta is the source, sending data out).
For these apps, admins can't manually configure the mapping — it's auto-discovered. Don't go looking for a mapping screen that isn't there.
Before saving, verify all required attributes are mapped. The preview feature uses color-coding — green for valid, red for errors — so misconfigurations are visible before you commit.
An optional push frequency setting controls how often mapped attributes update in the target system.
Watch for these in your own sandbox run:
→ Trying to hand-configure mapping on an entitlement-management app — it's automatic, not manual there.
→ Saving with a required attribute still showing red in the preview — it needs to be resolved first.
Sources: help.okta.com — usgp-map-attributes.htm
Next: Task 3 →