# Revoking admin doesn't enable all eligible admin buttons

**URL:** <https://meta.discourse.org/t/revoking-admin-doesnt-enable-all-eligible-admin-buttons/30060>\
**Category:** UX\
**Created:** [15 يونيو 2015، 10:46م UTC](https://meta.discourse.org/t/revoking-admin-doesnt-enable-all-eligible-admin-buttons/30060 "2015-06-15T22:46:57Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![fbender](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fbender/32/116736_2.png) [@fbender](https://meta.discourse.org/u/fbender)\
**Post date:** [18 يناير 2016، 2:46م UTC](https://meta.discourse.org/t/revoking-admin-doesnt-enable-all-eligible-admin-buttons/30060/5 "2016-01-18T14:46:31Z")

</div>

I think a force-refresh should be the way to go here.

Are the sessions updated for the affected user right away? Hypothetical situation: Admin is on rampage, I revoke rights and I expect him to be unable to do anything after I clicked the button. If he still can do anything he wants, there’s not much use in revoking his rights, isn’t it?

---

_[View the full topic](https://meta.discourse.org/t/revoking-admin-doesnt-enable-all-eligible-admin-buttons/30060)._