# Allow our forum gardeners to mark solutions? **URL:** \ **Category:** Forum Guide & Feedback\ **Created:** [December 18, 2023, 9:43am UTC](https://forum.ansible.com/t/allow-our-forum-gardeners-to-mark-solutions/2955 "2023-12-18T09:43:50Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\ **Post date:** [December 18, 2023, 9:43am UTC](https://forum.ansible.com/t/allow-our-forum-gardeners-to-mark-solutions/2955/1 "2023-12-18T09:43:50Z")
Howdy folks, One of the best features of Discourse is the [Trust Level system](https://blog.discourse.org/2018/06/understanding-discourse-trust-levels/) which means people gain more recognition & powers as they become more involved in the community. Notably, level 3 is hard to get and must be maintained - many things like editing topics etc comes at this level. We’re now seeing a few people earning this level organically (I did have to promote some people by hand to get things rolling, but that’s done) and that’s _awesome_ - thanks to those [that have earned it so far](http://forum.ansible.com/badges/3/regular). However, today the right to mark another person’s topic as “Solved” in #Get Help is reserved for TL4 (which can only be granted manually). I’m seeing people doing their best to encourage users to mark solutions in #Get Help, and I’m wondering if we should change this to a TL3 power, so that our community regulars can help to maintain the solved topics. Obviously if we see people marking solutions incorrectly we can change it back - I’m just trying to encourage the norm of having solutions. What do you think? I’ll throw up a poll here, but happy to hear detailed feedback too. _Poll ([view on site](https://forum.ansible.com/t/allow-our-forum-gardeners-to-mark-solutions/2955/1))_ ---
**Author:** ![chris](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/chris/32/293_2.png) [@chris](https://forum.ansible.com/u/chris)\ **Post date:** [December 18, 2023, 10:14am UTC](https://forum.ansible.com/t/allow-our-forum-gardeners-to-mark-solutions/2955/2 "2023-12-18T10:14:37Z")
I voted yes but its probably fine either way, being able to edit tags is the only thing I’ve felt the need to use so far. ---
**Author:** ![ptn](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ptn/32/481_2.png) [@ptn](https://forum.ansible.com/u/ptn)\ **Post date:** [December 18, 2023, 11:09am UTC](https://forum.ansible.com/t/allow-our-forum-gardeners-to-mark-solutions/2955/3 "2023-12-18T11:09:00Z")
Hi, Pretty much on the same boat as Chris. I’m not actively chasing unresolved threads, though some of us are (thanks to them ! -yeah, I’m looking at you @jbericat 😉 -), and it might help tidying things around a little ! I think people invested in this community so far are trust-worthy enough and showed good judgment in general. And as you said, we can always adjust / rollback if needed. ---
**Author:** ![jbericat](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jbericat/32/627_2.png) [@jbericat](https://forum.ansible.com/u/jbericat)\ **Post date:** [December 18, 2023, 2:07pm UTC](https://forum.ansible.com/t/allow-our-forum-gardeners-to-mark-solutions/2955/4 "2023-12-18T14:07:36Z")
Hello Greg! Actually this one’s a feature I was missing and that wanted to request myself, so I voted yes, obviously 🙂 Anyway, the idea I had (yes, I am “this” guy who always overthink everything) was more related with needing at least several votes from different L3 users to mark a response as the “official” solution (on my mind, three would be enough). Well, since I don’t even know if Discourse gives that option, and I don’t want to make your life even harder, I believe the rollback thing would be more than enough. Now I’ll take advantage of this thread, since is more or less related to what @chris said; another feature I also miss is to be able to edit the code snippets some users include on their posts, just for readability sake. But let’s just skip this side topic for now, since I’m aware that this is a L4 feat and it may also be kind-of “dangerous” to give L3 users this amount of power (it may lead to misunderstandings , etc etc) PS: I liked the “gardener” adjective so much 👨‍🌾🤣 ---
**Author:** ![jbericat](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jbericat/32/627_2.png) [@jbericat](https://forum.ansible.com/u/jbericat)\ **Post date:** [December 18, 2023, 2:13pm UTC](https://forum.ansible.com/t/allow-our-forum-gardeners-to-mark-solutions/2955/5 "2023-12-18T14:13:23Z")
Hey @ptn! You’re welcome mate. Actually it’s a real pleasure to have you here on the forum too, I’m learning a ton from your answers, really! ![](https://us1.discourse-cdn.com/ansible/original/2X/0/03bd23cb599c1a09f4b6990d6a3dd6ec0a496e14.gif) ---
**Author:** ![chris](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/chris/32/293_2.png) [@chris](https://forum.ansible.com/u/chris)\ **Post date:** [December 18, 2023, 2:20pm UTC](https://forum.ansible.com/t/allow-our-forum-gardeners-to-mark-solutions/2955/6 "2023-12-18T14:20:04Z")
> [@jbericat](#): > > Now I’ll take advantage of this thread, since is more or less related to what @chris said; another feature I also miss is to be able to edit the code snippets some users include on their posts, just for readability sake. But let’s just skip this side topic for now, since I’m aware that this is a L4 feat and it may also be kind-of “dangerous” to give L3 users this amount of power (it may lead to misunderstandings , etc etc) I suspect that all the current level 3 users would probably be fine as level 4 users — it would be easier to be able to assist in the formatting of posts directly, however advising users how to properly format their own posts is probably better, although it is more time consuming… but I agree that skipping this is fine. For what its worth I’ve set up a lot of Discourse servers and actively manage several (for example [community.coops.tech](https://community.coops.tech)) so I feel I know my way around… ---
**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\ **Post date:** [December 18, 2023, 3:09pm UTC](https://forum.ansible.com/t/allow-our-forum-gardeners-to-mark-solutions/2955/7 "2023-12-18T15:09:17Z")
I agree that there’s a lot of overlap between who _is_ TL3 and who we’d _like_ to make TL4. The slight niggle (and it is slight) is that TL3 is automatic (and so largely uncontroversial), while TL4 is manual-only. So is we want to be formal about it, that means making a process for promoting people - and I’ve not had chance to sit down and think about it yet. It shouldn’t _just_ be down to me and the other admins 🙂 ---
**Author:** ![jbericat](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jbericat/32/627_2.png) [@jbericat](https://forum.ansible.com/u/jbericat)\ **Post date:** [December 18, 2023, 6:33pm UTC](https://forum.ansible.com/t/allow-our-forum-gardeners-to-mark-solutions/2955/8 "2023-12-18T18:33:28Z")
> [@gwmngilfen](#): > > It shouldn’t _just_ be down to me and the other admins Absolutely! That’s another thing I like so much of this community ☺ Well, I believe I’ve already given my opinion about what other “powers” L3 members should have, so let’s just wait and see what other regulars think about it (now it’s me the one who’s gonna include another very active and really skilled one on this thread - yeah that’s you @utoddl 😉) ---
**Author:** ![chris](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/chris/32/293_2.png) [@chris](https://forum.ansible.com/u/chris)\ **Post date:** [November 15, 2024, 2:45pm UTC](https://forum.ansible.com/t/allow-our-forum-gardeners-to-mark-solutions/2955/9 "2024-11-15T14:45:49Z")
Incidently I just discovered that Trust Level upgrades in Discourse is not a one-way thing — users can be automatically downgraded, I believe this has happened to me, it doesn’t matter, but I’m glad it was probably done automatically and not manually 😉 . > **[Feature request: show TL3 requirements to people that have reached TL3 in the...](https://meta.discourse.org/t/feature-request-show-tl3-requirements-to-people-that-have-reached-tl3-in-the-past/315329)** > > What I’m referring to is this page I understand why it might be a undesirable thing to show someone the TL3 requirements - because they can just do the bare minimum inorganically to race to complete the requirements. But a reoccurring issue... ---
**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\ **Post date:** [November 18, 2024, 9:15am UTC](https://forum.ansible.com/t/allow-our-forum-gardeners-to-mark-solutions/2955/10 "2024-11-18T09:15:17Z")
That’s correct, but only for TL3 - that’s the only one that can be lost. Once you hit TL2, you’ll _always_ be that level, but TL3 depends on a level of recent activity, amongst other factors, so if you take a break from the community (which is entirely fair) then you drop down to TL2 (also fair, I think). And TL4 is always a manual grant, so that can’t be lost either 🙂 So, while I’m sorry that you lost your TL3 (just for a while perhaps? 😛) I think there is value in knowing that all TL3 people are _active_ people.