Okta Group Rules fail to execute for non-default user types, preventing the saving or previewing of rules for custom user profiles. Converting the affected users to the default Okta user type resolves this issue. Administrators are unable to preview or save a rule when creating group rules for users with a custom user profile.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Group Rules
• User Profiles

Okta group rules do not execute for non-default user types. This occurs whether using the preset conditions in the user interface or the Okta Expression Language option. If the expression is invalid for the default type, Okta prevents saving or previewing the rule, even if the previewed user is of the custom type. If the rule references a property that exists only for the default type and not the custom type, the expression treats the property as having a null value when Okta evaluates it for a custom user.

How are users converted to the default Okta user type?

Convert the users to the default Okta user type by navigating to the Directory, selecting the user, and changing the user type in the profile settings.

1. In the Admin Console, go to Directory > People.
2. Optional. Select a user type in the User Type list to filter the people list by that type.
3. Select a person in the Person & username column.
4. Click Change at the top of the user profile screen.
   
5. In the Choose user type list, select the User type.
   
6. Verify the attribute values for the user are correct.
7. Optional. Update any attribute values that did not transfer.
8. Scroll down and click Change user type.
   
9. Okta updates the user type at the top of the user profile screen.

Related References

• Universal Directory custom user types known issues
• Group Rule Limitations and Restrictions
• Change the user type