# Configure which groups see another group

**URL:** https://meta.discourse.org/t/configure-which-groups-see-another-group/261117
**Category:** Feature
**Created:** [April 9, 2023, 7:23pm UTC](https://meta.discourse.org/t/configure-which-groups-see-another-group/261117 "2023-04-09T19:23:31Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![PeakProsperity](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@PeakProsperity](https://meta.discourse.org/u/PeakProsperity)
#### Post date: [April 9, 2023, 7:23pm UTC](https://meta.discourse.org/t/configure-which-groups-see-another-group/261117/1 "2023-04-09T19:23:31Z")

</div>

Does anybody know if a plugin exists (or some other way of accomplishing this) that allows me to limit a group’s visibility to only members of a specific group?

For example:

- Everyone
- Logged on users
- Group owners, members, and moderators
- Group owners and moderators
- Group owners
- Members of specific group(s) [Input group name(s)] ← This option is what I want but does not currently exist.

Thanks for letting me know if there is a way to do this.

 ![image](https://global.discourse-cdn.com/meta/original/4X/b/e/4/be4f1efe7cc5b4ac03729537917d7dbd756b8f66.png)

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 10, 2023, 7:31am UTC](https://meta.discourse.org/t/configure-which-groups-see-another-group/261117/2 "2023-04-10T07:31:09Z")

</div>

You want group A to be able to see who is in group B but not be able to see who is in group C?

---

<div class="post-metadata">

### Author: ![PeakProsperity](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@PeakProsperity](https://meta.discourse.org/u/PeakProsperity)
#### Post date: [April 10, 2023, 5:01pm UTC](https://meta.discourse.org/t/configure-which-groups-see-another-group/261117/3 "2023-04-10T17:01:36Z")

</div>

Yes. In our particular use case we have the following primary user groups:

- Non-paying users
- Paying members

We also have user-driven secondary groups, for example:

- Western Massachusetts regional members
- Las Vegas members

We only want paying members to be able to browse and join the secondary groups, but right now that is not possible.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 10, 2023, 5:48pm UTC](https://meta.discourse.org/t/configure-which-groups-see-another-group/261117/4 "2023-04-10T17:48:34Z")

</div>

> [@PeakProsperity](#):
>
> We only want paying members to be able to browse and join the secondary groups, but right now that is not possible.

Ah. Thanks for the use case.

There should be a CSS solution that would hide those groups from people not in the paid group (it might need to be their primary group). Someone clever could bypass the css, but it might be good enough for your purposes.

To really enforce it, you’d need a plugin.

But why do you need the groups? If what you want to do is keep people who are non-members from seeing topics in those categories, you could just have the pay group be what controls access to the categories.

---

<div class="post-metadata">

### Author: ![PeakProsperity](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@PeakProsperity](https://meta.discourse.org/u/PeakProsperity)
#### Post date: [April 10, 2023, 5:56pm UTC](https://meta.discourse.org/t/configure-which-groups-see-another-group/261117/5 "2023-04-10T17:56:10Z")

</div>

> [@pfaffman](#):
>
> But why do you need the groups?

We’re looking to create more Facebook-style groups (hate to compare it to that, sorry) where members of those groups effectively get their own sub-forum, chats, etc. So, folks will need to be able to request membership into specific groups in order to gain access to those areas. Full discussion on the topic below:

> [@Discourse vs Invision Community](https://meta.discourse.org/t/discourse-vs-invision-community/252059):
>
> We are trying to make a decide between Discourse and Invision ([www.invisioncommunity.com](http://www.invisioncommunity.com)) for upgrading our WordPress blog’s commenting, forum, private messaging, and gamification components. Can anybody here provide any insights or opinions into the pros and cons of using Discourse vs Invision? It’s been hard finding reviews with head-to-head comparisons. Thanks. – Aaron

I understand there is core functionality coming on this at some point, and I’m hoping it is nice because if we can’t get this working in our community there is a good chance we’ll need to move to a different platform. The socialization/group aspect of our community is super important to our growth plans.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 10, 2023, 6:09pm UTC](https://meta.discourse.org/t/configure-which-groups-see-another-group/261117/6 "2023-04-10T18:09:22Z")

</div>

If you’re self-hosted, a plugin to allow access to groups only for those in a particular group shouldn’t be that difficult to create or commission. Maybe $1000-3000? Depending on features and specs that test that the plugin works as expected.
