# \[DONE\] Entity-level permissions **URL:** \ **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:** 20\ **Page:** 5
**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:** [November 1, 2023, 6:35am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/81 "2023-11-01T06:35:52Z")
> [@Ryan\_Dejaegher](#): > > would this be able to support something like adding view permissions to a third party client This is definitely a use case in scope ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [November 1, 2023, 9:27am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/82 "2023-11-01T09:27:05Z")
Will Entity-level permissions feature be released as one feature, or in multiple stages or multiple feature implementations? Any estimation of the first experimental feature of that? Thanks! ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [November 1, 2023, 9:29am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/83 "2023-11-01T09:29:46Z")
We are planning to work on permissions for the next 6 months, so more and more features will follow. First release may happen in ~2 weeks. It will have many limitations, but might work for some use cases like hiding important information from most users (1:1 interviews, salary, etc) and give access to specific part of hierarchy (everything related to Product A or Team X) ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [November 1, 2023, 9:54am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/84 "2023-11-01T09:54:02Z")
> [@mdubakov](#): > > but might work for some use cases like hiding important information from most users (1:1 interviews, salary, etc) Wow, that would be awesome! Is that on field level then? Or database level? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [November 1, 2023, 9:57am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/85 "2023-11-01T09:57:19Z")
It is on Entity level. For example, you have **One-on-One** database in **Employees** Space and it is connected to **Employee** database. You don’t want to share sensitive info to all users, so you restrict access to this space and only top managers have it by default. Let’s say you have Teddy as employee. So you can give access to human Teddy to an entity employee Teddy, and Teddy will have access to his employee record, all 1-1 meetings, and other connected entities, BUT Teddy will not have access to all other employees. ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [November 1, 2023, 11:52am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/86 "2023-11-01T11:52:39Z")
Thanks! Awesome! Given the new entity permission model, what would be your advised structure when you want to hide salary when salary is a number field that currently lives on entity employee? Would you then create a separate database for that field only or is there another smart way/workaround? ---
**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:** [November 1, 2023, 11:54am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/87 "2023-11-01T11:54:29Z")
> [@YvetteLans](#): > > Would you then create a separate database for that field only or is there another smart way/workaround? This is probably the best option, and for reasons other than access as well. For example if salary changes over time, you might want to link a person to more than one salary (each with a start date and end date). ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [November 10, 2023, 2:52pm UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/88 "2023-11-10T14:52:23Z")
> ---
**Author:** ![Minh\_Tri\_Do\_Hang](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/minh_tri_do_hang/32/6791_2.png) [@Minh\_Tri\_Do\_Hang](https://community.fibery.io/u/Minh_Tri_Do_Hang)\ **Post date:** [November 10, 2023, 3:18pm UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/89 "2023-11-10T15:18:56Z")
wow, I must admire that UI 's really impressive ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [November 10, 2023, 6:57pm UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/90 "2023-11-10T18:57:55Z")
Is it just me, or is that video too low-res to understand what’s happening? ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [November 10, 2023, 7:37pm UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/91 "2023-11-10T19:37:15Z")
Hmm, unfortunate recompression of the embedded Tweet. If you reference the original on Twitter it’s legible: [https://twitter.com/fibery\_io/status/1722980967927689245](https://twitter.com/fibery_io/status/1722980967927689245) ---
**Author:** ![anas.elbarkani](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/anas.elbarkani/32/8106_2.png) [@anas.elbarkani](https://community.fibery.io/u/anas.elbarkani)\ **Post date:** [November 12, 2023, 10:06am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/92 "2023-11-12T10:06:24Z")
Can’t wait to test the new entity-level permissions feature ! ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [November 16, 2023, 4:40pm UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/93 "2023-11-16T16:40:20Z")
The first experimental release is here: > [@Nov 16, 2023 / locked Entity permissions (experimental)](https://community.fibery.io/t/nov-16-2023-entity-permissions-experimental/5414): > > test_tube Entity permissions [share-entity] After a short private beta with a bunch of brave and helpful customers, we are ready to open entity permissions to a public beta. This is just the first release of many, so don’t get your expectations too high just yet sweat_smile. What’s new In addition to sharing entire Spaces, you are now able to share individual Entities with people who lack any Space access. Moreover, there is an option to extend access down the hierarchy: for example, to sh… Please let us know if it brings any value to your team and what’s missing if it doesn’t 🫣 ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [November 16, 2023, 5:23pm UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/94 "2023-11-16T17:23:04Z")
Being able to control access by a User _Group_ will be a huge additional benefit 👍 ---
**Author:** ![Lee\_Denny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lee_denny/32/8158_2.png) [@Lee\_Denny](https://community.fibery.io/u/Lee_Denny)\ **Post date:** [November 17, 2023, 11:20am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/95 "2023-11-17T11:20:52Z")
User groups would be so helpful - we use them in google workspace to manage our teams there ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [November 17, 2023, 11:45am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/96 "2023-11-17T11:45:03Z")
Welcome @Lee_Denny to the Fibery Community! 😄 ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [November 30, 2023, 6:18am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/97 "2023-11-30T06:18:29Z")
For the common scenario of users needing access rights to organic groups and organic group content , where the term group is not the permission groups in the admin section, but groups that can be created by users without admin intervention: If we have the same database ‘Task’ that is used across 100 organic groups, If organic group membership means that an organic group manager can approve individual membership requests I assume that: - There is a way to set permissions for each organic group enitity such that the tasks related to that entity can not be accessed when a user is not member of that group. ? ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [November 30, 2023, 6:40am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/98 "2023-11-30T06:40:10Z")
Also, if permissions can be depedent on an entity level relationship, then a feature/setting ‘required relationship’ is needed in the database field setting, to make sure that people do not forget to assign it to a group/project if that enables the permissions. ---
**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:** [November 30, 2023, 7:42am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/99 "2023-11-30T07:42:17Z")
Based on my understanding of what you are describing, this is possible with the new permissions model, using the ‘extend’ capability. That is to say, if a Team is linked to Tasks (one-to-many) it is possible to configure the permissions so that access to the Team automatically implies access to its Tasks. Eventually, it will be possible to automatically grant Project access based on a User relation to the Project (i.e. any User linked via the Member field has the permissions needed). ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [November 30, 2023, 8:24am UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/100 "2023-11-30T08:24:42Z")
> [@Chr1sG](#): > > the ‘extend’ capability That is amazing, looking forward to that! Would the ‘extend’ capability apply to the first level relationship, or can it extend unlimited in a hierarchical relationship tree? I’m thinking of for example top-down lockdown of: Company \> Department \> Group \> Team \> Project \> Milestone \> Task \> Dependent Task \> Action \> Note etc… [Previous page](https://community.fibery.io/t/done-entity-level-permissions/2163.md?page=4) [Next page](https://community.fibery.io/t/done-entity-level-permissions/2163.md?page=6)