These really need to be separate in group permissions. You may want to let users view profiles and not member lists. This really makes it hard to run a business site where people need access to profiles and have no business viewing the member list. Not to mention the memberlist has performance issues with large member numbers and bigger sites may want to shut that off all together. Maybe I'm missing something here? Been here a couple of years and this is the one pain I have come across. The rest has been aces and I couldn't be happier :) Great software

regards

I'd like to see the permissions separated as well.
And an additional permission for end users to set their profile to private (friends only) at their discretion (as the major social networks allow).

I've resorted to editing the members link out. Obviously can still access it if url is known. Would prefer no member list access at all setting while allowing profile access, setting for no profile access if user chooses friends only, and ability to separate these permissions as suggested above.

Is this added in 3.3 or?

i think it should be added in 3.3 considering its still in beta.

Given that the release is now in beta, I would bet all new feature enhancements have been locked. At this stage in a feature release, it is simply testing and bug removal.