# Ocultar contenido específico al administrador (un enfoque diferente)

**URL:** <https://meta.discourse.org/t/hide-specific-content-from-admin-a-different-take/110667>\
**Category:** Feature\
**Created:** [4 Marzo, 2019 21: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:** 13

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [5 Marzo, 2019 01:31 UTC](https://meta.discourse.org/t/hide-specific-content-from-admin-a-different-take/110667/13 "2019-03-05T01:31:01Z")

</div>

> [@Cozdabuch](#):
>
> 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.

That’s my point really, none of this is security, it’s security theatre at best giving the false impression of security where none exists.

It would be better to tackle attitudes to that, than create a facade of security - because if there is an incident where data gets out **none** of the above is going to protect you from being implicated.

---

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