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 ご回答ありがとうございます。Advisors というグループがあり、ブランドが特定の専門分野（マーケティング、セールスなど）を持つアドバイザーを検索できるようにしたいと考えています。アドバイザーは 3 つの専門分野を選択して、それらのグループに参加/購読します。ブランドがマーケティング担当アドバイザーに連絡する必要がある場合、その専門分野を選択したすべての人に直接連絡できます。
グループ名を使用して階層を作成することもできます。例えば：
アドバイザー
アドバイザー-マーケティング
アドバイザー-セールス
私はこの機能の実装を支持します。
この機能に賛成です。たとえば、異なる曜日に毎週授業があるコース（たとえば、あるクラスは毎週月曜日、別のクラスは毎週火曜日、すべてA100コース）を教えている場合、A100のすべての学生に対してグループを使用し、各月曜日/火曜日のクラスが親グループ内の個別のグループになるようなユースケースが考えられます。
そうすることで、コース全体の告知/教材を親グループに送信でき、個々の日（たとえば、月曜日のクラス）には独自のQ＆Aカテゴリを設定できます。
この新しい（非公式）プラグインは、この機能を見栄え良く提供します。