I have tested this item ✅ successfully on 914f5ca

This looks wrong to me. The solution is in the screenshot here #22884 (comment)

@brianteeman Shouldn't the superuser have access over any group? This behavior exists in other components

Groups which are used for ACL are different from the viewing access levels and the two systems should not be making assumptions based on the other. As I've said about a thousand times now, someone really just needs to sit down and refactor the code if you really want the viewing access level logic to behave differently based on the ACL code and stop plugging in random if (!Factory::getUser()->authorise('core.admin')) {} checks because that is not fixing the problem, that is just working around it.

@mbabker could you please make a outline what you suggest or provide a link to a solution?

Since there is this weird desire to couple the viewing access level system to the ACL system (two completely unrelated systems) and only for super users, a solution I have mentioned in the past is to adapt Joomla\CMS\User\User::getAuthorisedViewLevels() and its internals to assign all view levels to super users.

Other solutions include the deprecation of the viewing access level system in favor of a core.view or core.read ACL permission and have everything reside in one system, but given the ACL system's lack of scalability, this probably isn't something that will work well in the long run without a major refactoring of the ACL system.

ok, the access level is faster as the ACL I think, so returning all access levels for the super users would be the solution with less negativ impact. Maybe we find someone that could do this for J4.

I would close this here because its the wrong solution.