Hi @anirbandutta, thanks for your feedback! In your last paragraph, you hint at these groups being invite only. If that’s the case, what’s blocking you from making these groups Hidden, instead of Private, to avoid confusion altogether?
Other than that, we’ve made a clear distinction between the copy for Public groups (which say Join group) and Private groups (which say Request to join), particularly to avoid this confusion and to state that you’ve submitted a request (which can be denied).
HI @Sebastian, Thanks for engaging.
Allow me to explain the rationale here.
Let’s take “Hidden groups” out of the discussion, as their usage is very specific and obvious.
“Private groups” play an interesting role when I want to deliberately tease a larger population about the presence of a Select or an Elite program that exists ahead on the engagement road that they can participate in the future, but not yet. Could be a ‘Power Users group’, or something else I can tease users to level-up to achieve simply by it’s presence.
That’s where the answer to the, Request to join (but not granted) scenario becomes key to address whenever I tease a ‘Request to join’ CTA. I get to do that on the group landing page, but not on the /Groups listings page you see.
Not a Huge deal but an UX gap.
This is not applicable for “Public groups” where essentially I am announcing ‘come one, come all’, and no criteria applied to be a part of the group.
Hope that explains.
Updated idea statusNew→Open
We're also (about to be) running into this issue. We're starting to use groups for beta testing. For now, those groups are hidden and we invite users. But we want to set those groups to private, so people can request to join.
But, to be approved, they need to match the requirements (can't beta test a tv product if you don't have our tv service, for example). So, we need them to know what those requirements are. Currently there's no way to intuitively do this.
