Required tags should only be required based on type of user

UX
,
1

I have this tag group that I want to force on myself, as an admin, on a particular category, so I never forget to properly tag topics.

SCR-20251227-mfev
SCR-20251227-mfev454×431 21.9 KB

Since those tags are very specific and I don’t want them to be used by anyone else but me, I restricted who can use them:

SCR-20251227-mfli
SCR-20251227-mfli560×554 26.5 KB

Now, the issue is that when I try to create a new topic in that category as a non-admin, I can’t, because it requires me to add at least one tag, but all tags are restricted to admins:

image

My suggestion is that the “select at least 1 tag” should only be visible if at least 1 tag in that group can be used by users outside the group of users that’s restricted to. So, in this case, since all tags in the Danny Wyatt tag group are restricted to admins, but since I allow non-admins to post in the Danny Wyatt category, the “select at least 1 tag” warning and limitation, shouldn’t be there.

This allows me to force adding at least 1 tag as an admin, but non-admins can still create new topics and posts in that category.

3 Likes
Component to add a custom message to the Composer based on user and categories ID
2

I understand the idea, but as long as the tag requirement does not apply to administrators (which is currently the case), I don’t think this will solve your problem.

It still makes sense to apply requirements only to users who are allowed to use the tag.

1 Like
3

Thank you for sharing the link.
Unfortunately, I’m not sure I understand the issue that the user has/used to have?

From what I’m experiencing, the tags restrictions and limitations are being applied to admins, so I’m a bit confused as to why the user doesn’t have that applied to moderators?

4

It’s true that admins cannot use a tag that are limited to another category. However, they can create a topic without adding a tag even if a tag is required in the category’s settings.

Screenshot_20251227_165321_Firefox
Screenshot_20251227_165321_Firefox1157×349 69.6 KB

As an admin, leaving this empty will not block posting the topic. So I think

won’t work. You can still create a topic in that category without adding a tag

5

yup, thats the case afaik. Tag requirements are bypassed for admins.

We should really document that better, Ive seen another fairly recent topic hitting the same confusion (cant exactly remember it though)

Edit: oh here it is Required tag groups not being respected

2 Likes
6

I’m still a big fan of this idea, personally, as a way to address this problem more generally: "Regular mode" for admins and moderators (e.g. something like "sudo")

1 Like
7

Ok, so these seem to be two separate issues?

If so, maybe we should focus the conversation on what I original posted to avoid distracting from that original issue, since the one you guys are talking about already have open topics about it?

1 Like
8

Yes, I can see how that will still make my workflow not work as expected. The only thing is that it will show the text, so maybe I can see it and it will remind me, which is somehow helpful.

My issue is more related to other users not being able to post if the tags are required. For now I removed the restriction and I will have to force myself to remember. Hopefully these two issues are fixed in the future :crossed_fingers:

2 Likes
9

@alltiagocom I think my answer will not be exactly the one you expect. Currently I do not administer any Discourse forum so I can say that I am a beginner in the field.

On the other hand, I administered many forums under vBulletin then XenForo.

The administrator of a forum is not a super moderator, he is the one who manages the back office, the one we should never see on the public part.

I do not yet know the hierarchical system on Discourse but, in theory, the founder of a forum should create 2 accounts, an administrator, the shadow account, and a moderator account with maximum power that can be assigned to him. This case of tag bypass is typical (And there are probably many others), in the public management of its community it should not be a problem, and it is not if you are a moderator, not an administrator.

I don’t know if Discourse thought of these 2 different roles in this way but if so I hope my reflection can help you better manage your community.

1 Like
10

Thank you for your feedback.

The issue I exposed first, is not related to the admin, though. It’s related to the users who are not admins.

When I set a tag group that contains tags that can be seen (but not used) by people who are not admin such as this:

the users who are not admins, should still be able to create topics or reply to the topic, even if the topic requires at least 1 tag. In this case I’m using “admin” as the restriction, but it could be anything else, another group of users that can use the tag. So when I create a requirement for tags that are limited to a group of people, but then another group of people are required to use those tags they can’t use, it doesn’t make much sense.

It’s like saying: only people from Italy can enter this door, but we don’t allow anyone, regardless of country, to show their passport to confirm where they come from.

Hope it makes sense?

1 Like
11

Yes, you are right. It is a broader reflection that I proposed to you.

Does this problem, which I completely understand and which for me looks like a bug, is repeated if the group chosen is not Administrators but Moderators for example?

1 Like
12

It doesn’t matter which group(s) you select. You can also use a custom group. The result is always the same: users who aren’t in a group that is allowed to use tags from the tag group can no longer create topics in that category.

2 Likes