# Sharable entity fields or write permissions for selected fields only **URL:** \ **Category:** Ideas & Features\ **Tags:** permissions, sharing, rich-text\ **Created:** [October 14, 2026, 10:24am UTC](https://community.fibery.io/t/sharable-entity-fields-or-write-permissions-for-selected-fields-only/11420 "2026-10-14T10:24:23Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [October 14, 2026, 10:24am UTC](https://community.fibery.io/t/sharable-entity-fields-or-write-permissions-for-selected-fields-only/11420/1 "2026-10-14T10:24:24Z")
We work async and in very different time zones, like across oceans. Oftentimes, I need a stakeholder to cross out points in the acceptance criteria without me jumping on a call with them, so I’d cross those out myself. But I don’t want to give them write access to the entire entity, just this field, so they can check off valid points and leave comments on the ones that don’t work. Any chance to have this implemented? ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e29a24085f7c5a3976d8996eef71eee939bb9227.png) ---
**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:** [October 14, 2026, 10:58am UTC](https://community.fibery.io/t/sharable-entity-fields-or-write-permissions-for-selected-fields-only/11420/2 "2026-10-14T10:58:44Z")
I think this is the same as this, right? > [@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. That said, you cam already set this up with two entities with different fields which have a one to one relation, and a lookup/display fields from relation on entity view. It complicates the schema a bit, but it’s technically possible! ---
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [October 14, 2026, 11:03am UTC](https://community.fibery.io/t/sharable-entity-fields-or-write-permissions-for-selected-fields-only/11420/3 "2026-10-14T11:03:58Z")
I know I can and I did before – but that’s a pain in the ass to maintain. We have different teams/internal stakeholders. I want some of them (or just 1 stakeholder) to have access to AC points of the specific entities in my team’s space, so not all teams having the same access to that entity. ---
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [October 14, 2026, 11:08am UTC](https://community.fibery.io/t/sharable-entity-fields-or-write-permissions-for-selected-fields-only/11420/4 "2026-10-14T11:08:32Z")
Yes, sounds similar