# Nov 16, 2023 / 🔒 Entity permissions (experimental)

**URL:** <https://community.fibery.io/t/nov-16-2023-entity-permissions-experimental/5414>\
**Category:** Changelog\
**Created:** [November 16, 2023, 4:37pm UTC](https://community.fibery.io/t/nov-16-2023-entity-permissions-experimental/5414 "2023-11-16T16:37:19Z")\
**Posts on this page:** 1\
**Showing post:** 50

<div class="post-metadata">

**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:** [April 9, 2024, 10:36am UTC](https://community.fibery.io/t/nov-16-2023-entity-permissions-experimental/5414/50 "2024-04-09T10:36:22Z")

</div>

> [@YvetteLans](#):
>
> Does that also mean that an option "Can **view** and edit only entities assigned to them and create new ones” for a **whole space** will not happen?
> 
> So the ‘contributor’ role that we currently have on space level, but then **view** rights added.

Not only will this new option not happen, but we will likely deprecate the `Contributor` role once we have both DB access and automatic access for assignees.

The current Space access levels are a confusing mix of permissions on three levels:

- **Space:** who can share Space and create Views.
- **Database:** who can read and edit all the data inside the Space.
- **Entity:** who can edit specific Entities they are assigned to.

We are looking to untangle this knot to both make it obvious who gets access to what and unlock new use cases by combining DB and Entity access independently.

---

_[View the full topic](https://community.fibery.io/t/nov-16-2023-entity-permissions-experimental/5414)._