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.
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.
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.
3 Likes
csmu
(Keith John Hutchison - Ceiteach Seán Mac Úistin)
7
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.
We have a lot of groups (>60); this is overwhelming
Many groups are effectively sub-groups of other groups
If in a sub-group, a user would always need to be included in the larger group.
It is an administration headache to ensure that everyone is in all the groups they need to be in; and that the categories have all of the sub-groups in them (especially with sub-categories)
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.