Sure. Happy to expand.
We have a bunch of different teams at our company who contribute to our Community as SMEs for whatever piece of our product they’re responsible for. A group is created for each team, and when a team’s expertise is required in a topic, the topic is assigned to the team (and usually then assigned to an individual, who unassigns it from themselves when they’ve contributed all they can)
We don’t want to reveal to our users how this is all working. We try and keep expectations low (it’s free support we’re offering our open source users), we don’t want users to start asking “Why can’t you just assign this to the _____ team already??” – in fact, we don’t want our users to know these groups exist at all.
Usually, I’m all for radical transparency… but this works really well for us.
And, we want our internal users to be able to see all of these groups, the topics assigned to them, and have the ability to reassign to other groups.
But the group-level interaction permissions:
- Who can see this group?
- Who can see this group’s members?
- Who can @mention this group?
- Who can message this group?
- Who can assign this group
Are limited to the following permissions
This means that if we want to make sure all our internal users can see / interact with the groups the way we need them to, we have to grant at least moderator access. This isn’t ideal.
I hope this helps clarify the problem. Let me know if I can clarify anything further.