Epic Goal

• Add the functionality of the old Superuser Panel in the PatternFly UI without copying the old superuser experience 1:1
• Add new top-level menus for superuser functionality: User management, global registry configuration

Why is this important?

• We generally want the superuser to leverage as much of existing UI screens as possible to avoid duplicating list views in a separate superuser panel (e.g. orgs, users, etc)
• some superuser functionality does not fit in the existing organization and repository management screens, so we need new screens, e.g. for user management
• other superuser functionality should probably be grouped together in a new menu that deals with the registries general configuration (this likely resembles the new superuser menu but we shouldn't call it like that)

Scenarios

1. As a superuser I want to disable a user: so I go to the new UI, select the new users menu, search for the user by name or email address and then disable it from there - regular users don't see this menu
2. As a superuser, I want to disable an organization: so I go to the new UI, search for the organization by name in the existing organizations screen and then disable it from there, the disable option in the context of an org is only presented to superusers
3. As a superuser, I want to set a global message: so I go to the new Settings menu (working title) and configure global messages there

Acceptance Criteria

• All existing superuser functionality must be covered in the new UI, but not everything has to be implemented (duplicated) in a new Settings menu

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>