I’m looking for a tag-based permission on topics. My use case is that I have some topics that belong to a certain category because the way they are created (via RSS to be specific). But I want to restrict some of the topics to be member-only (i.e. not public).
It would also work for me if I could set permissions on chosen topics, but it doesn’t seem possible either.
Are you solving this already in some other way (like moving them to a different category)?
If this could be done with tags instead, would it need to be controlled by the RSS integration itself? Or is it something you’d apply after the topic is created?
I’m working around this by moving them to another category. It is not ideal, and I hope nothing breaks.
Yes, I apply it manually after seeing the topic.
Which part is the bigger problem for you?
This one is the bigger problem for me.
I am wondering if maybe a custom automation could maybe be made to automate the move?
Op currently from my understanding Tags have very little permission controls except tag only can be used by this group and for staff can also set whether it is viewable. I believe at present you would need a custom plugin. But if it is also for RSS feeds might also complicate it. So a category would be best with the permissions required to limit who can access/see topics
This doesn’t matter much for me, as the tag is assigned manually too.
It would also work for me if an individual topic can be set member-only.
그러면 결국 수동으로 태그가 지정되기 전에 해당 주제가 일정 기간 동안 공개된다는 뜻이 됩니다.
따라서 #customization:theme-component를 커스텀해서, 특정 그룹에게 주제를 x 카테고리로 이동하고 y 태그를 적용할 수 있는 옵션을 제공해야 할 것 같습니다.
No, I don’t want to move it to another category. I have to move it because lack of permission settings.
Then you will be looking at creating a complex plugin or sponsoring one.
The benefit of a Custom Theme Component moving the post and applying the tag makes it one click vs several.
To add permission system similar to categories is not a simple task.
The other and maybe simpler task would be to instead of using a tag, would be to switch it to a category with the name of the tag instead of using tags
OK, thanks for the explanation.
This may be the road forward for me.
운영자(Op)의 게시물을 확인하고 있습니다. 해당 주제들이 운영자가 이동시키고 특정 그룹이 지정된 경우에만 볼 수 있기를 원하신다면, 자체 호스팅(self-hosted) 환경이라면 #customization:plugin 채널에 있는 ‘Private Topics’ 플러그인을 사용할 수 있습니다. 이 플러그인은 주제 작성자와 설정된 그룹만 볼 수 있도록 합니다.
호스팅 서비스를 이용 중이라면, 해당 플러그인이 포함된 플랜이 필요합니다.
해당 플러그인으로 이동하는 링크입니다.
This plugin still ties to a category, and it doesn’t make a difference for me than use the category permissions.
Yes it does but can go with the alternative to name a category the tag name and move topic to the Category. The plugin then makes it so only the Op and configured group(s) can view and respond in that topic
That is if course if you only want the Op and specific group(s) able to view and interact.
If you could maybe give an example of how the purpose of this direction works. Just to make understanding the direction you need/want to accomplish.
Another option would be to use a main Category where ppl post. Then create Subcategories using the Tag names. The Subcategory(tag) could have refined permissions and you would only have to edit the Category to Category\Subcategory
Great, thanks for clarifying. Let’s focus on this part then.
Can you help me understand why this is a problem for you and/or your community? What’s wrong with these topics ending up in a different category? (Does making the private category a subcategory of the public one help? Are you already doing that?)
If you can share any screenshots or links that help to illustrate, even better.
I want to restrict the visibility of some topics based on the content and moderator’s decision, i.e. they should only be visible to logged-in users. Usually this is done by moving them to a category that has such permissions configured.
I also have setup the RSS Poll plugin to repost articles to another dedicated category on our forum (it’s called “Planet” because this functionality was provided by the now-dead planetplanet.net software).
Now you see, a reposted-from-RSS article could also be the kind of topics that needs to have restricted visibility, but a topic can’t belong to two categories. On the other side, a topic needs to be put into a category, so most RSS articles end up in a one category and a few in another. I don’t feel good about this inconsistency.
I wonder if this theme component might be a good fit: Gated Topics in Category
It has an enabled tags setting that sounds like what you might be looking for.
Why is this an inconsistency? After all, they do have different permissions attached to them. And why would a different tag not be an inconsistency?
If the more restrictive category is a subcategory of the other one then you won’t even really notice.
E.g. users may subscribe to the RSS category and miss some topics.
Because I can add multiple tags to a topic.
I haven’t started to use nested category yet. The forum was mitigated to Discourse only recently.
This one seems promising! I’ll give it a try later.
For logged in user switch category permission See from everyone to Trust Level 1 Trust Level 0.
The Subcategory is still part of the main category. Though you may or may not need to tweak or add to your RSS setup.
This could be the case with having to educate users. But your current feed might be fine with using a nested subcategory