I definitely see the merit of this feature. When we run workshops or have demo environments we may not want all emails to be public!

We are adding groups support in #4235 including a global "Everyone" group. Perhaps each group (including "Everyone") could have a Member visibility: (true)/false setting.

Alternatively, we could restrict the page and API routes for admins only. As a user, I will want to know what groups I'm in, but not necessarily who the other users are in the group/deployment.

@ammario suggested doing this via an env variable to disable viewing users for all non-admins. I agree.

If a user wants to see their groups, that should be in their profile. Re-using an Admin tab like Users is not an enterprise good look IMO even if it's read-only.

If a user wants to see their groups, that should be in their profile. Re-using an Admin tab like Users is not an enterprise good look IMO even if it's read-only.

Maybe a user should be able to view his own groups and the other members in the same groups at maiximum.

Any plans for these guys?
I think it is required after we allow the opening coder to the public using GitHub signup.

No one should be able to view all the other members except the user admin or owner.
@bpmct

I think it's a fine default that regular users can't see everyone. I don't think we should add an additional configuration knob yet.

But the regular users withy a member role can see everyone on the latest version.

Hey @bpmct! I found at least 2 similar request issues referring to the same problem:
#4550
#5002

Do you think that we can unify/deduplicate all these?

BTW I commented on the design here. It would be great to clarify it, and I don't mind where the response lands :)

Yep. Closing in favor of #5002