Epic Goal

• Implement a Superuser panel in the new UI and optimize performance for superusers

Why is this important?

• Quay administrators require a dedicated location to configure things related to the maintenance of Quay, such as GeoRep
• Superusers have the ability to view all orgs, users and repos and this can lead to performance degradation so optimizations such as pagination should be adopted.
• API adjustments may also be necessary for positive performance

Scenarios

1. Superusers are able to access a new section of the UI that contains admin specific features like GeoRep
2. Non-superusers are not able to access the superuser panel
3. The UI should not appear sluggish and orgs and repos should load in approximately the same time as for a non-superuser

Acceptance Criteria

• Tests are updated to account for the new scenarios
• Docs has been notified of this new default behavior and that the old UI will be fully removed at the end of the year in the 3.13 release.

Dependencies (internal and external)

1. Superuser API endpoints for manipulating entities in user accounts:
   1. robots
   2. autopruning policies

Previous Work (Optional):

1. N/A

Open questions::

1. TBD

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>