![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Community admins/moderators: moderation queue action subscription
Title:
Community admins/moderators: moderation queue action subscription
Area:
communities, notifications, entries, moderation queue
Summary:
Create a subscription for action (acceptance and rejection) for community moderation queues. Make this subscription available only to users who have access to see the moderation queue.
Description:
Community moderators may currently receive notifications for new submissions to their community's moderation queue.
It would also be useful for them to get notifications about moderation queue action, possibly from themselves, but definitely from other moderators.
The notification should include:
The username of the moderator who made the action, what the action was, what community this is in, the username of the user whose submission it was, the time the submission entered the queue and the time the action was made, the note (if any) the moderator left, the entry's title, contents, and possibly other relevant metadata (tags, location, mood); if this action was an approval, a link to the entry as posted.
(Should this be sent for items that are marked as spam? I can think of arguments in both directions: against: in case of legitimate spam it is useless overhead that will only bother the other moderators, emailing known spam may alarm email providers; for: if a moderator is marking things as spam that are not spam (either accidentally, mistakenly, or maliciously) the others should know, moderators who become accustomed to messages about queue action may be surprised when they see an entry come in but find it gone with no notification about why.)
This notification should only be available to people with access to see the moderation queue, which in practice is only moderators, but in terms of practical community oversight might need to include the community administrators.
The subscription should be separate for every community, and should (if possible for business reasons) not count against the subscription slot limit.
(Related: an on-site moderation queue log.)
This suggestion:
Should be implemented as-is.
20 (35.1%)
Should be implemented with changes. (please comment)
4 (7.0%)
Shouldn't be implemented.
0 (0.0%)
(I have no opinion)
33 (57.9%)
(Other: please comment)
0 (0.0%)
no subject