How to find administrators of a group in /design Appian 18.2?

Administrators of a group are just those assigned the "Administrator" permission level on the group's rolemap + the group's creator. You can find that by selecting a group and clicking the "Security" button in any Appian Designer UI or from the Security menu option when viewing a specific group's member (screenshot below)

 

You can read about a group's security in our documentation: docs.appian.com/.../Group_Management.html

That shows you who has administrator permissions of the group but doesn't show the administrators of the group. I verified this in other environments and they're not the same.

Jamal Case
What's the disparity you're observing?

I've updated the post with a screenshot to show that group security is not a one to one mapping of the administrator tab in /designer. I was expecting all members that was in /designer administrator tab to be in group security.

Hi Jamal Case (jamalc823)
I looked at the screens you added.
One of the chief complaints about groups management in old /designer was that it was too difficult to identify precisely how a user or group became a member of a parent group.
There was a great deal of confusion about direct vs inherited permissions.
For example, if you added group X to group Y, all the members of group X were displayed as members of group Y.
You could try to delete an individual member (of group X) from group Y all day long and it wouldn't disappear.
That's because those users inherited their permissions in group Y via group X.

So, looking at your screenshots - when you look at the old /designer groups>administrators tab, you're being shown all direct + inherited members of that group. This display proved out to be more confusing than it was useful.

Today, the product does a much better job of helping us designers distinguish between direct vs inherited relationships between users and groups.
Looking at the newer /designer group security dialog, I can see that you've got two groups in there. Those are the groups that have been directly added to the group you're inspecting.
I suspect that if you audited all the groups and users inside these two groups, you'd have your 1:1 mapping.

As a designer, at first, it's an adjustment to look at it this way, but the product team put a lot of thought into this change, and it reflects what the design community has wanted for a long time.

Hi Jamal Case (jamalc823)
I looked at the screens you added.
One of the chief complaints about groups management in old /designer was that it was too difficult to identify precisely how a user or group became a member of a parent group.
There was a great deal of confusion about direct vs inherited permissions.
For example, if you added group X to group Y, all the members of group X were displayed as members of group Y.
You could try to delete an individual member (of group X) from group Y all day long and it wouldn't disappear.
That's because those users inherited their permissions in group Y via group X.

So, looking at your screenshots - when you look at the old /designer groups>administrators tab, you're being shown all direct + inherited members of that group. This display proved out to be more confusing than it was useful.

Today, the product does a much better job of helping us designers distinguish between direct vs inherited relationships between users and groups.
Looking at the newer /designer group security dialog, I can see that you've got two groups in there. Those are the groups that have been directly added to the group you're inspecting.
I suspect that if you audited all the groups and users inside these two groups, you'd have your 1:1 mapping.

As a designer, at first, it's an adjustment to look at it this way, but the product team put a lot of thought into this change, and it reflects what the design community has wanted for a long time.

Thank you for this explanation. I understand now.

Thanks for this answer. I was working with a customer who was concerned about the differences here, and you clarified the changes and the reasoning behind them nicely.

Thank you Robert for this detailed explanation