Skip to main content
Version: Omada Identity on-premises 16.0.0

Legacy UI removal

Mandatory migration — Version 16

The new UI is mandatory as of Version 16. All users are automatically transitioned upon upgrade. There is no opt-out.

Note that this requirement applies to the UI framework only. The new access request UI and the new approval UI are not enforced by this change — they can still be configured independently. Unless explicitly changed in configuration, the system continues to use the existing access request and approval flow.

The legacy menu-based user interface (black menu/submenu navigation) has been removed as of version 16.0 and is no longer supported. This change primarily impacts navigation, layout, and user experience. The transition includes:

  • Replacement of the legacy black menu/submenu navigation with:

    • New Main menu
    • New Setup menu

  • Introduction of the new homepage experience.

    • Dashboard configuration as the homepage is no longer supported.

  • Replacement of the legacy Compliance Workbench with the new Compliance Workbench.

  • Modernized list views and form layouts in the portal.

Important

The removal of the legacy UI does not automatically change business processes, such as:

  • Access request workflows
  • Approval processes
  • Role models
  • Policies
  • Existing configurations

However, some processes may use modernized pages within the portal.

The portal provides access to the following capabilities:

  • Tasks page. However, access can be configured independently.
  • Access request experience
  • Non-human Access request
  • Extend access
  • Approvals
  • Identities form and list view

The navigation model has been reorganized to improve usability and streamline access to features:

  • Menu items have been restructured.
  • Some items have been renamed to better reflect their functionality.
  • Several options have been relocated within the menu hierarchy.

The updated structure provides improved discoverability, reduced duplication, and more logical grouping of features.

Impact on customizations​

If your system includes customizations or modifications to standard menu items, the following may be required after upgrading:

  • Reordering of menu items: Custom items may no longer appear in their intended position due to structural changes.
  • Verification of renamed items: Ensure any dependencies or references align with updated menu naming.
  • Validation of navigation paths: Adjust links, shortcuts, or documentation that depend on previous menu locations.
info

Existing permissions and access controls remain unchanged. Functional capabilities are not removed, but some may be accessed differently via the updated menus.

Technical Preview features

The following features are available as Technical Preview:

  • Service Library
  • Eligibility Filtering in Access request
  • Enhanced list views and forms

Technical Preview features are subject to change and should not be used in production without proper evaluation.