# \[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:** 1\ **Showing post:** 13
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [September 29, 2020, 4:48pm UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/13 "2020-09-29T16:48:00Z")
Michael, it was good to hear from you re: permissions, would be curious if you could shed any light on whether you guys will also be looking at Type-level: > [@Type-level permissions](https://community.fibery.io/t/type-level-permissions/501): > > Hi guys, I know this is something you are thinking about, but I wanted to add the request here as a sort of “upvote” to make a case to prioritize this. Here is my situation and why this would be useful: I am trying to set up all all “work items” in my team (small software development with some marketing, HR, content, etc.) can be tracked in one place. So stuff like development chores, recruiting tasks, recurring posting of blog articles each week, etc. These are all “work items,” and not “t… Many of the tools I’ve used have nice ways to handle these levels of permissions. One of my favorite, which is central in Wrike, and Asana, and ClickUp - who I might loosely consider a similar “triumvirate” of “Task Managers” like Airtable/Coda/Notion is within the “nocode” sub-space, all do this: - If you @mention a user within a comment stream, they get added **just to that particular task** - You can “share” lists/folders/projects to a particular group. So in the case of Fibery, I think you have a great chance with your existing hierarchy to do a similar approach that would be very familiar to those coming in from these tools - and perhaps others who handle things similarly like Hive, Monday, Teamwork Projects, etc. So in Fibery this would work out as: - You can access particular users to a Type, much as you do now with a whole App - via mentioning a user, they get access to an **individual** Entity only. The addition of the Type-level permission makes it easier to break down groups of Entities within an App. I have this need in Task Management I am running in Fibery, where I have groups of Tasks in Types that I’d like to have only certain users see, and not the whole App’s worth of Types. Hope that’s useful and curious to see how you guys will solve this! --- _[View the full topic](https://community.fibery.io/t/done-entity-level-permissions/2163)._