# Permissions - entities vs views

**URL:** <https://community.fibery.io/t/permissions-entities-vs-views/1868>\
**Category:** Ideas & Features\
**Tags:** permissions\
**Created:** [August 3, 2021, 9:46am UTC](https://community.fibery.io/t/permissions-entities-vs-views/1868 "2021-08-03T09:46:17Z")\
**Posts on this page:** 1\
**Showing post:** 33

<div class="post-metadata">

**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:** [August 17, 2022, 9:22am UTC](https://community.fibery.io/t/permissions-entities-vs-views/1868/33 "2022-08-17T09:22:02Z")

</div>

This is in plans and we call it Entity-level permissions. We are going to start implementation soon. You can check some details here.

> [@\[DONE\] Entity-level permissions](https://community.fibery.io/t/planned-entity-level-permissions/2163):
>
> Why? So far all the [access management](https://help.fibery.io/en/articles/5350066-permissions) in Fibery happens on the App level. The only way to share an individual Entity (ex. a Task) with a teammate is via read-only [external sharing](https://help.fibery.io/en/articles/5303654-sharing-entities-and-documents) poop Introducing Entity-level permissions will unlock new opportunities: Collaborating with clients As we’ve learned, Fibery is a surprisingly good fit for many service companies: think digital agencies and development studios. A good fit, that is to say, before we start talking about access management. …

---

_[View the full topic](https://community.fibery.io/t/permissions-entities-vs-views/1868)._
