I’d love a feature that allows us to nest groups.
For example, let’s say that I have a volunteer organization. There are different groups of volunteers with different functions. One group of volunteers is working on the online forum. Another group is working on an upcoming potluck party.
I’d love to be able to add someone to project based sub-groups, let’s say “online-forum” and “potluck-party” and have everyone in these groups automatically be placed in a “volunteer” group.
What problem are you trying to solve?
You can give category access to any number of groups, so you can give access to the volunteer category to all of those subgroups, and, perhaps, but even bother with a volunteer group.
I want to be able to message the group. Let’s say we have a volunteer-only appreciation event. I’d like to be able to @volunteers in order to notify everyone.
I don’t want every volunteer to be notified every time a topic is created in the Volunteer category, so setting every group to watch the category wouldn’t work. I want to reserve the messages for special occasions.
How are your users getting into Discourse? Are you using any form of identity management, or single sign-on?
You could create announce categories for the announcements. But you’d need a plugin to force having them watched.
I think that would be easier than the plugin to create sub groups.
People can only sign up using emails at the moment.
We mostly add people by invite.
We have a public facing part of the forum for discussions, announcements, and events and jobs postings that are open to anyone.
We have an internal facing part of the forum for projects that only people who are volunteering for that project have access to.
When someone joins a volunteer effort who isn’t already on Discourse, we invite them into the relevant group and all communications about the volunteer effort goes through Discourse.
Are you saying we could create an announcements sub-category within the volunteers category and use a plug-in like https://meta.discourse.org/t/ability-to-force-subscription-to-a-category/66357/2? That could work for the messaging use case. It still creates redundancy, where I need to give access to the volunteers category to every volunteer group AND add the same groups to the plug-in, but it’s certainly better than having redundancy at the user level. Thanks!
I continue to think having sub-groups and parent groups is a good idea. Categories are about organizing topics and groups are about organizing people. They often overlap but aren’t the same.
I’m looking to have sub groups to be public only to parent or relate groups.
The problem I’m wanting to solve is enabling volunteers to be able to freely join or leave groups that relate to the categories.
Something like tag_groups. Being able to determine which groups are ‘public’ for that categoru.
I’ve thought of another reason to have parent groups, or at least ways to categorize groups.
Right now I have multiple groups that serve different purposes.
Project Groups
Affinity Groups
Event Alumni
Right now there’s no easy way to categorize them. I could potentially have a naming mechanism, but something like
seems really clunky to me, and long!
I imagine tag groups were created for the same reason.
Our group problems that need a solution:
While there is room to tidy up and hide many of our groups, it would certainly simplify things for us if we had sub-groups.
In Active Directory, this makes maintaining the group structure and the veracity of the people in them enormously easier - especially with a larger organisation. But it is also likely pretty curly to implement and will break many things (such as plug-ins). It has certainly taken our Microsoft colleagues about a decade to sort out!
A plugin could add a custom field, parent group, to a sub group that would add users to the parent group when they joined. That would be fairly straightforward.
Things would get stickier knowing whether to remove someone from the parent if they left the child.
我支持这个功能的实现！
Is there already a feature for creating subgroups? I found a post here but it doesn’t provide the solution but mentions a plugin is feasible.
My use case would be:
Parent group:
Child groups:
And here we can use @PythonUsers to notify all specialists, admin and basic users. But if I just want to request the input of just the python specialists I use the @PythonSpecialists group tag.
话语的方向是相反的。你创建类别（可选地包括子类别），并允许人们在这些类别中加入讨论。如果他们想收到通知，可以通过蓝色铃铛为每个类别设置通知偏好。
你还可以创建群组，可以在话题中用 @ 提及，让他们参与对话，如果你喜欢的话，可以使用类似你指定的系统，例如 @pythonusers（所有使用 Python 的人）和 @python-specialists（仅限 Python 专家）。
但理想情况下，你应该先确定你的类别结构。
我们对类别的使用方式与群组不同，我需要在单个群组内创建子群组。这样做可能吗？
你好，珍妮！不，没有创建子组和在层级中可视化它们的功能。不过，你总是可以创建具有重叠成员的组。
你能否详细描述一下你希望做的事情？
@tobiaseigen 非常感谢您的回复。我们有一个名为“顾问”的群组，我正在寻找一种方法，让我们的品牌能够搜索具有特定专业领域（例如营销、销售等）的顾问。因此，顾问会选择 3 个专业领域并加入/订阅这些群组。这样，如果品牌需要联系营销顾问，他们就可以直接联系到所有选择了该专业领域的顾问。
你总是可以使用组名来创建层次结构。类似这样：
顾问
顾问-市场
顾问-销售
我支持这个功能的实施。
为这个功能点赞。我可以想到一个使用场景，如果你在教授一门课程，该课程每周的课程安排在不同的日子（例如，一节课是每周一，另一节课是每周二，都在A100课程中），那么可以使用一个群组来容纳所有A100的学生，其中每周一/周二的课程是父群组中的独立群组。
这样，整个课程的公告/课程材料可以发送到父群组，而每天的课程（例如，周一的课程）有他们自己的问答类别。
这个（非官方的）插件可以很好地提供此功能：