# 管理者から特定のコンテンツを非表示にする（別のアプローチ）

**URL:** <https://meta.discourse.org/t/hide-specific-content-from-admin-a-different-take/110667>\
**Category:** Feature\
**Created:** [2019 年 3 月 4 日午後 9:37 UTC](https://meta.discourse.org/t/hide-specific-content-from-admin-a-different-take/110667 "2019-03-04T21:37:19Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Cozdabuch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cozdabuch/32/139120_2.png) [@Cozdabuch](https://meta.discourse.org/u/Cozdabuch)\
**Post date:** [2019 年 3 月 5 日午前 1:27 UTC](https://meta.discourse.org/t/hide-specific-content-from-admin-a-different-take/110667/11 "2019-03-05T01:27:13Z")

</div>

> [@pfaffman](#):
>
> Good point. The other option would be to create a plugin that disables impersonation.

people would love this. there would be a lot of boards who could use this.

* * *

The group has agreed to use this for a trial period of 3 months. They won’t spend $ on dev work until its officially adopted. That would be my intent long term. But this is to take away the “easy” ways to snoop without leaving logs. Yes impersonate leaves logs, but reading messages through the user’s profile tab/messages button does not. I simply want it to be “obvious” that I am intentionally looking where I shouldn’t so they can trust the system.

Obviously it’s totally possibly to parse the DB through the root. But if I was doing that, they’d have bigger issues with me or any future admin.

---

_[View the full topic](https://meta.discourse.org/t/hide-specific-content-from-admin-a-different-take/110667)._