# Real granular permissions

**URL:** <https://community.fibery.io/t/real-granular-permissions/11432>\
**Category:** Ideas & Features\
**Tags:** permissions\
**Created:** [October 16, 2026, 9:10pm UTC](https://community.fibery.io/t/real-granular-permissions/11432 "2026-10-16T21:10:29Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [October 17, 2026, 6:28am UTC](https://community.fibery.io/t/real-granular-permissions/11432/3 "2026-10-17T06:28:59Z")

</div>

> [@Field-level permissions](https://community.fibery.io/t/field-level-permissions/2799):
>
> Problem: Some fields within an entity may need different permissions than others. E.g., if a Task has a “Due Date” field, this ideally would not be editable by the Assignee - only by a “manager”. But the Assignee will have Editor permission for most everything else in the Task. A hack might be to use a lookup to a Due Date field that exists elsewhere, but that complicates changing the Due Date for someone who does have permission.

---

_[View the full topic](https://community.fibery.io/t/real-granular-permissions/11432)._