TYPO3 Core

Thank you. I just took a look at the current 10.4-dev branch.

The backend user overview is better now, because the current approach makes it easier to see all assigned permission to a user, which is really good. :)

However, as someone who has to maintain those groups and assigments I would like to see why a certain permission has been assigned to the user, which group is responsible that the user has this permission. If I want to check why a user still has the permission X (when he shouldn't) I still have to go through all the groups to find the group responsible.
Imagine you have multiple people who maintain these groups. Sooner or later people make errors and assign permissions to the wrong groups. In order to find those errors later, you have to check every group and find the group which has the wrong permission.
So, a good workflow would be that you see a compare view of be groups and can easily spot the error and directly correct it in that view (so you don't have to go back to the group and correct the permission).

So, in case of error handling nothing has changed, I think.

I saw that you have added a feature #90826 for comparing be user groups. In the current version I don't see that feature (I can only compare users). I think that is a good feature.

Without seeing the user interface of that be group compare view I assume it works like the user comparison, where you can compare multiple users by adding users to a compare view and click the "compare"-button where you see every user in a compare view?
So, does the be group comparison works the same way: You can make a list of groups you want to compare by manually adding be_groups to a list and then click a "compare" button?

If that is the case, would it be possible to integrate a "compare be groups" button directly in the users properties which would - if clicked - add all assigned usergroups from that user to the be group comparison view? Perhaps group dependencies can also be made visible in that compare view?

So, I think finding a solution for an optimal workflow to handle be groups/users and permission errors was my intention to start this issue/feature discussion. I'm happy that it's not forgotten because I think that this is a part where TYPO3 can be improved a lot.
If not for the upcoming LTS, maybe for the next. Maybe other users want also to contribut their thoughts. So, I would be against closing this discussion. :)