26% of Part II — hands-on configuration, not multiple choice.
5 tasks · this deck covers task 3 of 5
↑ User Management OverviewNot every user in an org is the same "shape." A contractor might need different attributes than a full-time employee. User types are how Okta lets different populations have genuinely different profile structures.
A user type is a profile template in Universal Directory. When created, it starts as a copy of the default Okta user profile — the 31 base Okta attributes — which you can then customize further.
Creation is duplication-based: copy the standard profile, rename it (e.g. "Contractor"), then add whatever custom attributes that population actually needs.
This is a hard ceiling. Plan user-type usage deliberately — you can't create an 11th type "just in case."
If someone needs a different type later, that's not an edit — it requires a separate profile entirely. Get the type right at creation time, because there's no "move this user to a different type" button.
Because each type can independently customize its own attributes, this sets up directly into Task 4 (adding a custom attribute to a user type) — that task is about going deeper into one specific type's attribute configuration, not creating the type itself.
Watch for these in your own sandbox run:
→ Creating too many experimental types and hitting the 10-type ceiling.
→ Assigning a user to the wrong type, then looking for a way to "switch" it — there isn't one; it needs a new profile.
Sources: help.okta.com — usgp-usertypes-about.htm
Next: Task 4 →