# \[DONE\] Entity-level permissions

**URL:** <https://community.fibery.io/t/done-entity-level-permissions/2163>\
**Category:** Ideas & Features\
**Tags:** permissions, sharing\
**Created:** [October 29, 2021, 2:32pm UTC](https://community.fibery.io/t/done-entity-level-permissions/2163 "2021-10-29T14:32:55Z")\
**Posts on this page:** 1\
**Showing post:** 71

<div class="post-metadata">

**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\
**Post date:** [October 2, 2023, 8:07pm UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/71 "2023-10-02T20:07:28Z")

</div>

@Chr1sG I understand the limitations. As @Oshyan pointed out, I guess the options we are suggesting (either having [conditional control over fields](https://community.fibery.io/t/setting-field-ui-properties-based-on-conditions/5226) and/or [multiple layouts](https://community.fibery.io/t/individual-layouts-for-a-node-hide-fields-etc/995)) would be half measures from a permission-perspective but they would also have other useful benefits. So they can be suggested as possible workarounds (along with separate dedicated database as @mdubakov indicated) each with their own limitations, so creators can choose based on their needs. For example, in many cases, hiding or locking fields is not so much a matter of security but convenience/user experience.

---

_[View the full topic](https://community.fibery.io/t/done-entity-level-permissions/2163)._