Okta is releasing a significant enhancement to the End-User Settings (EUS) experience, moving from EUS v1 to the new EUS v2. This change separates the End-User Dashboard and End-User Settings pages into two independent applications. This gives administrators greater flexibility and control, allowing them to integrate these components more easily and creatively across environments.

The phased rollout will begin in July 2026 for Okta customers. The EUS v1 application will be fully deprecated once the rollout is complete. This article outlines the steps to ensure a smooth transition. This is a required migration for all OIE customers.

• All Okta Identity Engine (OIE) organizations
• This change does not apply to Classic orgs

The legacy EUS v1 app was embedded directly within the End User Dashboard app. By separating these components in EUS v2, it enhances user accessibility and reduces the complexity of your configuration for both workforce and customer identity users. To focus on innovation and new features dependent on this modern framework, Okta will not support both versions of the EUS app long-term.

Customers must review their integrations with the End User Settings to prevent breaking changes upon the deprecation of EUS v1. Take the following steps well in advance of the deprecation date.

Step 1. Identify Existing Integrations in your Preview orgs

 
Action: Review any custom code or integrations that interact with the current End-User Settings page in your Okta preview orgs.
Rationale: Since the EUS v2 contains an updated user experience, any direct integration may need to be updated to achieve parity with existing integrations.

Step 2. Review Sign-On Policies

 
Action: Navigate to your Okta Admin Console and review the application sign on policies to review any custom policies that may need to be applied to the new “Okta End User Settings" application.
Rationale: The new standalone "Okta End User Settings" application will receive the default sign on policy and does not inherit any custom policies that are applied to the “Okta End User Dashboard” application by default. Applying any custom sign-on policies to the new standalone "Okta End User Settings" application may be needed for maintaining security parity if you have configured custom access rules (e.g., MFA, network zones) for your dashboard.

Step 3. Test the New Experience

 
Action: Once the EUS v2 is enabled for your org, thoroughly test the new, independent End-User Settings page.
Rationale: Verify that your required security posture is enforced and that your updated integrations function as expected with the EUS v2 standalone app.

Note: For customers who encounter integration issues after upgrading to EUS v2, contact Okta Support for assistance.