# Hide People/User for non-admins

**URL:** https://community.fibery.io/t/hide-people-user-for-non-admins/5439
**Category:** Ideas & Features
**Tags:** permissions
**Created:** [November 23, 2023, 1:50pm UTC](https://community.fibery.io/t/hide-people-user-for-non-admins/5439 "2023-11-23T13:50:14Z")
**Posts on this page:** 1
**Showing post:** 19

<div class="post-metadata">

### Author: ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)
#### Post date: [March 11, 2025, 9:54am UTC](https://community.fibery.io/t/hide-people-user-for-non-admins/5439/19 "2025-03-11T09:54:06Z")

</div>

I think that with Users becoming more like a real database, there might by some workaround like automatically creating a “Profile” every time a “User (system)” entity is created. It’s linked, maybe has some lookups for the name and profile pic, but not for the email. Then in the access templates, just not allowing access to the related people fields. BUT This would mean Fibery would need to [expose the system relations](https://community.fibery.io/t/expose-system-relations-in-entity-permissions/8391) (Created by field). To restrict the view to that. But auto link the “Profile” based on email of the “created by” and thats the one people have access to. Could work quite nicely! (Only down side is that comments, and in turn, “Thread view” would not be functional until [comments are converted to real entities](https://community.fibery.io/t/comment-fields-and-inline-comments-to-be-entities-with-fields-comments-database/4602/3) or [Allow any entity to be used as a comment](https://community.fibery.io/t/allow-any-entity-to-be-used-as-a-comment/8294) for thread view.)

---

_[View the full topic](https://community.fibery.io/t/hide-people-user-for-non-admins/5439)._