Discourse for Teams가 점점 더 큰 팀들의 관심을 끌고 있는 만큼, 이미 수행할 수 있는 작업들을 모두 수행할 수 있을 뿐만 아니라, 해당 카테고리에 접근 권한이 있는 모든 카테고리에 대해 전체적인 관리자 권한을 부여하지 않고도 하위 카테고리를 생성하고 관리할 수 있는 카테고리별 관리자를 지정할 수 있으면 유용할 것입니다. 이 기능이 다른 Discourse 사이트에서도 유용할 수 있다고 생각합니다. 이 아이디어에 대해 논의된 바가 있는지, 그리고 이를 추가하는 것이 실현 가능한지 궁금합니다.
12개의 좋아요
Building on the above, I would like to suggest a couple of improvements.
Disclaimer: we are using discourse for teams. Some of our use case are very different than for an open community.
You can configure discourse to allow moderators to create categories and manage groups.
This is quite useful because:
- we want to limit the number of admins
- we want to allow many people in the organisation to create categories, which can be achieved with the above. The reason for this is that we are creating categories for teams or projects.
- It’s also useful to have many people that have moderator perms like splitting topics.
However there is one specific issue: moderators can manage ANY group, which means they can add themselves to a group giving access to a restricted category. For instance, we have a leadership category and don’t want a moderator to add himself to the leadership group. It would be logged but that’s not enough.
It would be incredibly useful to split this setting into two:
- Allow moderators to create categories
- Allow moderators to manage groups
Alternatively, maybe there could be some restriction on which group can be managed by whom, so that a moderator can’t manage ANY groups but a specific list. I am not sure how it would work in details.
Thank you 
11개의 좋아요
이 게시글들을 별도의 Contribute > Feature 토픽으로 옮겼습니다. 다른 사이트 소유자들도 이에 관심이 있는지, 그렇다면 어떻게 구현하는 것이 가장 좋을지 파악하고 싶기 때문입니다.
2개의 좋아요
This Feature Request would be very interesting for our “Discurse as a social intranet” approach, so count me in.
7개의 좋아요
Thanks, Ralf! Can you tell us some more about your community and how you are using Discourse, and how categories and category moderators fit into it? Feel free to PM me if you prefer not to share sensitive info about a private community.
2개의 좋아요
Hi, I think it is just basic security practice. If I want to appoint someone to create categories and moderate those categories, that’s a ton of trust. But it’s not so much trust that I want this person to have the capacity to manage ANY group in the community.
Consider Facebook. You can create a group/category (they are kind of identical), and manage it, but that’s it. Same with Reddit. You can create a subreddit, but it only gives you moderation privileges for that subreddit.
6개의 좋아요
Hello,
In addition to all the moderator features given to the “Category Moderator” feature (which is great by the way, thanks !), I would love to be able to give the ability to Category moderators to moderate (and manage) their category AND sub-categories.
I’ve already read a thread mentioning that big communities (> X thousands of members) should probably split their discourse forum into multiple forums. However in the case of our community (a sport related one) we want multiple small entities (“clubs”) to have access to their own top level category and be able to moderate its content, but also manage their own sub-categories. We don’t want to give full-instance moderator rights to those “club owners” as it gives a lot of privileges that we prefer to keep for a limited set of people in that community.
I’ve also read a comment (can’t find the discussion now, sorry) about “trusting moderators”, which I agree with, but in the community we are trying to build we have pretty independent entities (each “club”) which work well by their own, have existing identified responsible owners, but we also have transversal work groups (which span across multiple “club”), thus the need for a unified Discourse instance.
Is there any chance to add the possibility for those Category moderators to create sub-categories?
Many thanks for your help and for the amazing work done in Discourse software 
4개의 좋아요
I’m juggling a similar thing. We have a Spanish language category with several sub-categories. My Spanish moderators are in a group so they can only manage those categories. The way the “About” page is set up, they are listed six times for every category I’ve granted the group moderation ability for. Not a huge deal but it looks weird.
I recently read that a moderator of a main category inherits moderation privileges for sub categories, so I removed group permissions from the subcategories but left them as moderators for the main “Discussion in Spanish” category.
One of the mods had their first post in a sub category thrown into the main moderator “review” queue. They reported they no longer have the mod-wrench in the sub categories. I impersonated to verify and they have the timeline mod wrench on the main category but not in the subs. They have a mod wrench to “Create Staff Notice” and can edit posts in the main category but not the subs.
The About page looks correct now, but what I read I’ve either misunderstood or isn’t working correctly. I don’t need the Spanish mods to create categories, but I need them to moderate main and sub categories.
I can live with the repeat listings on the About page I suppose - perhaps it might be a better fix to program the About page that lists mods to just not display every sub category if they’re also a mod in the parent category?
Or is there a better way to set them up as category mods that’s not putting them in a group and grant that group mod permission in the category setup? Perhaps I should just give them TL4 and allow them to also submoderate the rest of the board?
2개의 좋아요
Thanks for this, Hanon. Can you clarify what the problem is that you are seeking to solve? You are mainly concerned about the duplication on the about page?
We recently made changes to the about page, and category moderators are no longer shown at all. Next time you update, you will see the change.
2개의 좋아요
It’s not a huge fatal issue, but just my OCD tidiness. I’d resigned myself that the Spanish mods were shown multiple times on the about page, and we were considering other foreign-language mods and I didn’t look forward to the FAQ page showing even more repeats. I read something on here that main category mods inherited mod ability on the subcategories so thought “perfect”. I removed their group from the sub category permissions and left their group in the main category “allow groups to mod” setting, and today they’re reporting they can’t mod the sub categories and (this may be a separate thing) one of the regular mods reported one of their posts was delayed since it had to be approved for some reason.
(We’ve been toggling to approve new registration since we’ve had an influx of trash accounts signing up, so that last part may be related to that.)
I saw the update that the About page is getting a re-design, so if that solves most of this I’m happy.
2개의 좋아요
We are updated to Discourse 3.4.0.beta3-dev and here’s what my About page looks like; our Spanish mods who are in a group set to allow moderation in Category setup in multiple categories:
Again, it’s not causing problems except for my OCD “tidiness” reflex because it makes the About page bigger than it needs to be. I understand if this is not of great concern since it’s cosmetic and I can figure out a new strategy like making them TL4 users instead of putting their group in every category.
1개의 좋아요
Okay, I finally got the About page to display correctly.
Apparently in the latest update we have offered to us and installed (3.4.0.beta3-dev) it’s still considered an “experimental” feature I had to opt into.
1개의 좋아요
교육 프로그램 내 모든 교육 과정과 여러 연구 그룹을 호스팅하기 위해 Discourse를 사용하려고 계획하고 있습니다. 두 접근 방식 모두 교육 과정 = 최상위 카테고리 + 여러 그룹(교육 과정 팀 및 교육 과정 참여자) 또는 연구 그룹 = 최상위 카테고리 + Discourse 그룹이라는 구조를 촉진합니다. 이 둘은 여러 개의 격리된 Discourse 인스턴스에 자연스럽게 매핑되지 않습니다. 교육 프로그램은 동일한 학생 집합(cohort)을 공유하며, 연구 그룹은 일반적으로 완전한 Discourse 인스턴스를 운영하기에는 규모가 너무 작고, 공유된 지식에서 이점을 얻습니다.
반면, 두 경우 모두 상당한 수준의 자율성을 위임하고 싶습니다. 교육 과정 강사들은 각자의 과정을 다른 방식으로 구성하기를 원하고, 연구 그룹은 연구 프로젝트를 위한 하위 카테고리를 생성하기를 원합니다.
두 요구 사항은 모두 최상위 카테고리와 그룹을 구성할 수 있는 권한을 위임하는 기능으로 가장 잘 해결될 수 있는 것으로 보입니다. 하나의 가능한 방법은 카테고리와 하위 카테고리에 대해 "manage"라는 더 높은 권한 계층을 도입하는 것입니다. 이는 그룹 소유자가 자신의 그룹을 관리하는 방식과도 유사합니다.
1개의 좋아요
완벽함을 위해 추가로 말씀드리면, 다음 링크도 확인했습니다.
이 제안은 투표 수 기준으로 두 번째로 높은 기능 제안이며, 아직 구현되지 않은 제안 중에서는 1위입니다. 이번 요청은 이 제안과 밀접한 관련이 있지만, 카테고리 관리자가 구체적으로 무엇을 할 수 있어야 하는지에 대해 더 명시적으로 서술하고 있습니다.
설정을 더 자세히 살펴보니, 위임이 용이하지 않은 또 다른 권한 공백이 있음을 깨달았습니다. 바로 태그 그룹과 카테고리 전용 태그의 관리 권한입니다. 구체적으로 다음과 같습니다:
- 태그 그룹은 특정 카테고리로 제한될 수 있습니다.
- 태그 자체는 어느 정도 동적으로 관리되도록 설계되어 있습니다. 기본 권한에 따르면 TL3(3급 팀 리더)가 태그를 생성할 수 있습니다.
- 그러나 태그를 특정 카테고리로 제한하는 작업은 스태프만 수행할 수 있습니다.
즉, 카테고리 관리자는 전역 설정에 영향을 주지 않고 자신의 카테고리를 독립적으로 조직할 수 있는 자율성이 없습니다.
팀에 간단한 질문을 하나 드리고 싶습니다: 아래 게시물에서 언급된 카테고리 재구성 계획에 권한 재구성도 포함됩니까? 
안톤, 이 주제에 정말 관심이 많으신 것 같네요! 최근 4개의 게시글이 모두 안톤 님의 것입니다. 
조금만 기다려 주세요. 이 주제는 저희의 관심 목록에 올라가 있지만, 해당 프로젝트는 이제 막 시작 단계입니다:
2개의 좋아요