# User Trust Level Manually isn't being set

**URL:** https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021
**Category:** Feature
**Created:** [July 25, 2014, 12:21am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021 "2014-07-25T00:21:25Z")
**Posts on this page:** 16
**Page:** 1

<div class="post-metadata">

### Author: ![hb\_ryn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hb_ryn/32/50458_2.png) [@hb\_ryn](https://meta.discourse.org/u/hb_ryn)
#### Post date: [July 25, 2014, 12:21am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/1 "2014-07-25T00:21:25Z")

</div>

[https://meta.discourse.org/t/feature-mod-manually-sets-a-users-trust-level/8021/19?u=hb\_ryn](https://meta.discourse.org/t/feature-mod-manually-sets-a-users-trust-level/8021/19)

Is all I’ve found on the issue, but when trying to demote someone from trust level 3 \> 2 this is what happens:

[Click](http://puu.sh/apPw0/b5cc25723c.png)

Going into admin and under trust levels, if I try to “x” out the user and hit “save” it reloads the page and essentially does nothing again.

---

<div class="post-metadata">

### Author: ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [July 25, 2014, 3:48am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/2 "2014-07-25T03:48:07Z")

</div>

I just tried on our forum and it worked a treat.

I went to one of my test accounts Admin page  
Changed the dropdown from TL2 to TL1  
Saved  
The test account’s Profile then showed TL1 and the TL2 Badge was no longer there.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [July 25, 2014, 3:59am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/3 "2014-07-25T03:59:33Z")

</div>

Are you on latest? Be on the latest check in.

---

<div class="post-metadata">

### Author: ![hb\_ryn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hb_ryn/32/50458_2.png) [@hb\_ryn](https://meta.discourse.org/u/hb_ryn)
#### Post date: [July 25, 2014, 4:27am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/4 "2014-07-25T04:27:50Z")

</div>

Yep, on the latest, I’m attempting from 3 \> 2, could it be that the auto-promotion to level 3 is denying the demotion?

[http://puu.sh/aq5jT/2b9fe9ca2b.png](http://puu.sh/aq5jT/2b9fe9ca2b.png)

Any specific setting that can be preventing this from happening?

Edit:

A tested around a bit more and apparently I can promote/demote someone, but I cannot demote them past any trust level they earned on their own. As in, if I didn’t promote them manually to trust level 2, or 1, or 3, whichever one it may be, then I cannot demote them past the trust level they earned. Which is an issue, because the auto-promotion to level 3 is apparently pretty easy to attain and some demotion is required.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [July 25, 2014, 6:00am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/5 "2014-07-25T06:00:56Z")

</div>

If you think TL3 is too easy to get, why not increase the criteria for it in the site settings so it is harder to get?

---

<div class="post-metadata">

### Author: ![hb\_ryn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hb_ryn/32/50458_2.png) [@hb\_ryn](https://meta.discourse.org/u/hb_ryn)
#### Post date: [July 25, 2014, 12:58pm UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/6 "2014-07-25T12:58:12Z")

</div>

That doesn’t exactly fix the bug though.

Figured a slight work-around. Setting the requirements ridiculously high allows them to be demoted, but regardless demotion by a staff member shouldn’t be prevented if the user fits the requirements of the trust level.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [July 29, 2014, 6:44am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/7 "2014-07-29T06:44:28Z")

</div>

@neil I can confirm I am unable to demote myself to trust level 2 on meta.

@codinghorror was is this meant to be supported (the ability to demote a user below their automatically granted trust level)

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [July 29, 2014, 7:04am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/8 "2014-07-29T07:04:38Z")

</div>

No, I don’t think we planned to support it in V1.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [July 29, 2014, 7:15am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/9 "2014-07-29T07:15:07Z")

</div>

recategorizing this to feature then.

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [September 13, 2014, 9:13pm UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/10 "2014-09-13T21:13:01Z")

</div>

Sent in a fix for being re-promoted to TL3:

[https://github.com/discourse/discourse/pull/2796](https://github.com/discourse/discourse/pull/2796)

---

<div class="post-metadata">

### Author: ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [September 14, 2014, 1:13am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/11 "2014-09-14T01:13:03Z")

</div>

Does this just prevent the user from getting TL3 or can it forcibly lock someone into TL 3 when they haven’t met the requirements for it (the scenario we find ourselves “kind of” wanting)

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [September 14, 2014, 1:13am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/12 "2014-09-14T01:13:37Z")

</div>

It does both - if it’s set to locked, they are neither considered for promotion nor demotion.

The updated promotion requirements page has correct text to explain that.

---

<div class="post-metadata">

### Author: ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [September 14, 2014, 1:14am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/13 "2014-09-14T01:14:33Z")

</div>

Yep, note to self: Next time read the GitHub comment before replying!

Sorry about that, I should have saw that. Thanks for the quick response (even though I was hoping to edit my prior post before you saw it…)

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [September 30, 2014, 3:31am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/14 "2014-09-30T03:31:50Z")

</div>

This now works 100%

You can demote / promote a user to any trust level.

If you move them below the trust level the deserve their trust level will be **locked** meaning that they will not be able to get out of this trust level until you unlock it.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [September 30, 2014, 4:23am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/15 "2014-09-30T04:23:15Z")

</div>

Hmm I think the locking should be an explicit Boolean checkbox.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [September 30, 2014, 5:48am UTC](https://meta.discourse.org/t/user-trust-level-manually-isnt-being-set/18021/16 "2014-09-30T05:48:36Z")

</div>

Lock / Unlock is explicit. I just found it very annoying to lock up a lower trust level without implicit logic.

EG.

- Try to change trust level to 0, “Sorry you can not do this cause trust level is not locked”
- Lock trust level at 3
- Change trust level to 0

It just felt majorly awkward for no real gain. So instead we just treat moving trust level down beyond what you are allowed as an implicit lock and display that as well. Moving up to TL2 will not cause an implicit lock, but moving to TL3 will.
