I have to say I'm not thrilled with the current implementation of User Groups and Admin Groups. There's no check for duplicates on the group name. So I can very easily create 'Customer Service Reps' in the User Groups, and then create a 'Customer Service Reps' group in Admin Groups. Now I have two entities in ac_Groups with identical names.

From a data model perspective, this is a major problem. I can no longer trust _groupRepo.LoadForName("Customer Service Reps") to deliver a unique group. In fact, it seems to return only the first group matching the name specified.

I often leverage security groups as a way to categorize specific users for a specific feature or task. Now I can no longer rely on the name of the group to be unique.

I think ultimately the confusion lies with having two different pages to view any group. User groups and Admin groups, from a data perspective, are the exact same entity. But we have two different pages to manage them. So it's very easy to check User Groups and create something that duplicates what is already created in Admin Groups.