I just wanted to say how you can work around this:
You don’t give the rights to the user, but create an extra moderator-account, which has only read and write rights for the specific category, they should moderate.
As we use SSO-Login we plan to automize this login as moderator and back to the user, by just one button, so we will have a one-click moderator mode. This has the side effect, that people can’t moderate right away, but have to change into that mode. This might be also not such a bad idea, given the extensive rights, that are not even marked as moderator-rights.
The only thing that’s then missing for us is the user-administration. It would be awesome, if you could have something in the preferences to take that right from them moderators. In our case the moderators will get group-specific user-administration rights in the sso. They can only administrate users who are yet without group or in their own group.
Maybe these work-arounds could also give some idea how you could implement category specific moderators?
First of all, I’d like to express my most sincere gratitude, I’ve used many forum scripts this far, and Discourse beats them all in most fields.
I want to voice for this functionality, though. We run regions-driven community, and we need the ability to appoint cat-specific moderators. As we’re non-profit community, I can’t offer any financial support, I’m afraid. But as a software tester I can offer my proffesional services, if it helps, @codinghorror
I started looking at this issue last night in the context of a larger project I’m working on.
First, after looking at the relevant code for this I would reiterate what the Discourse team has already said. Implementing this specification would be a huge hairy change. From a ‘core’ perspective I think It makes complete sense to postpone it, and maybe not do it at all.
For me at least, it seems that the issue is really one of triage. I need the ability to limit a moderator’s attention to a particular category. I want them to be able to focus on that category without getting distracted by notifications from other categories.
Completely restricting access to moderation actions outside of a assigned category seems like more of an edge case. If someone is going to get moderation powers, and be told that they are assigned to a specific category, it is unlikely that:
a) they will regularly exercise their powers outside of their assigned category; and
b) if they do, it is unlikely that this exercise will conflict with the overall moderation goals of the site.
In the unlikely event of both ‘a’ and ‘b’ being incorrect, then they probably shouldn’t be a moderator anyway.
Indeed, there may well be situations in which moderators assigned to a particular category will provide useful support in categories in which they are not assigned to.
So I’ve started a plugin I call “Category Moderator Lite” to implement this narrower ‘workflow-orientated’ version of category-specific moderation.
Whether this should be a user setting or a category setting (or both) is worth considering.
While notification levels are typically user settings, I think there are also arguments for this being a category list that entails user notification levels (i.e. the approach taken in the Category Moderator Lite plugin).
There are instances in which it is useful to have the concept of ‘assignment’ to a particular category, even if that assignment does not entail permission restrictions. e.g. if you want to add a list of the ‘assigned’ moderators to the discovery category UI to tell users who’s ‘in charge’, e.g. something like
Not to say that this particular UI feature should be a part of a core update, but more that having a list of moderators related to a particular category could be useful.
The need to ‘guide attention’ of some moderators to specific categories is both a user-level issue and a more global site-level ‘management’ issue. For my purposes, I don’t really want to pose moderation notification levels as a ‘choice’ for category-specific moderators. I more want to set it up as a workflow.
That said, making this a user-level setting is simpler from a technical perspective. As far as I can tell there are no existing category settings that entail updates to specific users’ notification levels. So it would be a new type of relationship.
And, if there were a user setting I would still find that useful. It would simplify the Category Moderator Lite Plugin a fair bit. I would hide it from the user settings UI and just use it on the server.
As far as a core update is concerned, I’m not sure what form of category-specific moderation notification settings people would actually use. I know a category-level setting makes more sense for me, for the reasons mentioned above. From the posts in this topic, I get some sense that the issue is also a ‘site-level’ management issue for other folks as well, which suggests that a category-level list which entails notification levels for specific users may be useful.
Thinking from the POV of a first-time Admin who is trying to set this up (or modify it), I think it would be most intuitive to find category specific mod settings under the current Category security settings.
I’ve been playing with this in our new installation of Discourse (we’ll be launching live hopefully soon) and it seems to be working well, and should give me precisely what I need. I think this is an ideal solution, and very elegant (As well as providing expandable opportunities for mod-specific access categories)
I’ve started looking into this for my discourse, and am struggling a bit to understand what features are provided now for category-specific moderators. Am I right that at the moment it’s simply a category moderators listing on the about page and access to Category Group Review/Moderation? In my testing I have not found any other handy functionality, like whisper access.
Would it be possible for someone in the know to create a #howto topic on category-specific moderation and keep it up to date with the latest functionality provided? I’d be grateful.