Hiding trust level

Product Support

AI-generated summary

In a support discussion titled ‘Hiding trust level,’ jenni_alencar asked how to hide Trust Level 0 from new members to avoid them knowing their status until they reach the next level. simon clarified that Trust Level 0 isn’t visible to users and offered solutions: disable the TL1 welcome notification via site settings, customize its text, or disable the ‘Basic’ badge. To hide the trust level display on user profiles entirely, simon suggested adding CSS to hide the trust level field. rahim123 appreciated the solution but requested visibility for admins only. Stephen provided a refined CSS snippet that excludes staff members: body:not(.staff) { .user-main .about .secondary dd.trust-level, .user-main .about .secondary dt.trust-level { display: none; } }. rahim123 confirmed both CSS methods work and acknowledged that while users could inspect HTML to reveal hidden elements, this is not a major concern. The discussion concludes with a practical workaround using CSS to hide trust levels from regular users while preserving visibility for staff.

1

Hello!

I couldn’t find how can I hidding the trust level 0 for the new members.

I want that new members don’t know that they are basic, just know the when they are in the next level.

Or, if not’s possible, hide notification.

4

I could be wrong, but I do not think that trust level 0 is displayed anywhere that users can see. When a user is granted trust level 1, Discourse sends a notification telling the user that they have been promoted to trust level 1. You can disable this notification by deselecting the send tl1 welcome message site setting.

You can also customize the message by going to your Admin / Customize / Text section and searching for welcome_tl1_user . This search will return three text templates. You would need to customize the system_messages.welcome_tl1_user.title to change the “Welcome TL1 User” text. You might also want to change the system_messages.welcome_tl1_user.text_body_template text.

When users achieve trust level 1, they are also granted the “Basic” badge. You can disable this badge on your Admin / Badges page. To disable the badge, scroll to the bottom of the Admin Basic badge form and deselect the “Enable badge” checkbox.

If you would like to keep the Basic badge enabled, but remove “Trust Level 1” from the badge description, you can customize the badge description by going to Admin / Customize / Text and searching for basic_user. This search will return three text strings. The one you will want to change is badges.basic_user.long_description.

When you visit a user’s profile page and see something like this, the user has trust level 1 (basic), not trust level 0:

image
image1188×302 19.5 KB

The easiest way to remove this would be to hide this trust level field for all trust levels with CSS. Adding the following CSS to your theme should work:

.user-main .about .secondary dd.trust-level,
.user-main .about .secondary dt.trust-level {
    display: none;
}

This would hide the trust level field on the profile page for all trust levels. If you would like to display higher trust levels, but not display trust level 1 (basic), this could be accomplished with a theme component. Let us know if you only want to hide the trust level of basic users and we will try to help with that.

5

Thanks, this gets close to what I need. (I definitely like having trust levels, I just don’t want users to know what they are so as to avoid rivalry and competition.) The only thing is that I would find it useful as the administrator to see trust levels in the user profiles. Could this be included as a configuration option to show or hide for different groups of users?

6

AFAIK the above CSS still works, you just need to wrap it in the below so that it doesn’t apply to members of staff:

body:not(.staff) {
    .user-main .about .secondary dd.trust-level, .user-main .about .secondary dt.trust-level {
    display: none;
    }
}
7

Yes, I can confirm that the CSS works, both the previous one and your tweak for me. Thanks a lot for the help. I suppose if someone really wanted to they could still inspect the HTML and see those hidden elements right? That’s why I was thinking that a config option to disable it might be better, but that’s really not too much of a concern though.