Allow group admins to set default subscription setting / change and apply in bulk

Created on 8 June 2020, about 4 years ago
Updated 5 February 2023, over 1 year ago

When this module is first added to a given site the site may already have a host of existing users. While the site admin could message users asking them to set up their group_subscription settings it would be better to have a way to set defaults for all existing users in a batch process.

Add a tab to the module configuration page where admins can set the master switch settings, site-wide announcements and group subscriptions for all users in a batch.

There is another scenario where a site admin may create a new group and manually add a bunch of users to it. The site admin may want to set up all group members with a default group subscription setting. We should either provide a mechanism the site admin (or group admin) can use to apply a specific subscription setting to all group members (at any time) - and/or - provide a group setting to serve as a default subscription type to be applied to new users as they join.

✨ Feature request
Status

Active

Version

3.0

Component

Code

Created by

πŸ‡¨πŸ‡¦Canada JayDarnell Guelph, Ontario

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¨πŸ‡¦Canada JayDarnell Guelph, Ontario

    I'm still unsure of the best way to implement this but I think its important. Group admins need to be able to specify the default subscription settings for their groups in some way. The users can still change the settings if they so choose but defaulting to disabled means users will never get notifications unless they know they need to set them up.

    Allowing an admin to bulk change user subscriptions within a group after the fact is also useful in some situations but does go against the spirit of the module in that the end user ultimately has control. I have a lot of work to do to get the 3.0.x branch streamlined but I'm keeping this issue around to revisit as soon as I can.

Production build 0.69.0 2024