# More granular rights or adjusted rights

**URL:** https://community.fibery.io/t/more-granular-rights-or-adjusted-rights/6096
**Category:** Ideas & Features
**Tags:** permissions
**Created:** [April 19, 2024, 3:35am UTC](https://community.fibery.io/t/more-granular-rights-or-adjusted-rights/6096 "2024-04-19T03:35:10Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)
#### Post date: [April 19, 2024, 3:35am UTC](https://community.fibery.io/t/more-granular-rights-or-adjusted-rights/6096/1 "2024-04-19T03:35:10Z")

</div>

Hi, so having groups-based rights is great and while I’m overall happy with the groups, but would like to suggest some adjustments if we want to keep a simple one-dimensional list:

1. `Creator`: Can configure the databases → IMHO this should be called `Admins` as they are the space admin and can configure the space
2. `Editor`: Create and edit entities → IMHO, this should be split into `Creator`, who can create new entities and `Editor`, who can only edit existing entities
3. `Contributor`: Create entities and edit ones assigned to them → IMHO, these should not be able to create entities, and only edit the ones assigned to them
4. `Viewer`: View but not edit → IMHO, this should be split into `Commenter`, who can always participate with inline or discussion comments and `Viewer`, who can only read and not add comments.
5. `No access`

The more granular approach, instead, could be a two-dimensional list (no access, view, comment, edit vs. no creation, create new, configure space)… the key differentiator for me is really that some people I want to disallow to create new entities, as I want to have a tightly controlled space structure, but then allow users to contribute contents.

Also, not all entities have assignees, just like documents, whiteboards and so forth seem to live on a different spectrum than entities (and views)

Thanks!

---

<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 22, 2024, 2:55pm UTC](https://community.fibery.io/t/more-granular-rights-or-adjusted-rights/6096/2 "2024-04-22T14:55:04Z")

</div>

Yep, this is close to what we have in mind for Database-level access — hopefully, coming later this year.

Quoting our [conversation](https://community.fibery.io/t/nov-16-2023-entity-permissions-experimental/5414/50) with Yvette:

> [@Nov 16, 2023 / lock Entity permissions (experimental)](https://community.fibery.io/t/nov-16-2023-entity-permissions-experimental/5414/50):
>
> 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.

---

<div class="post-metadata">

### Author: ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)
#### Post date: [April 22, 2024, 3:35pm UTC](https://community.fibery.io/t/more-granular-rights-or-adjusted-rights/6096/3 "2024-04-22T15:35:58Z")

</div>

Thanks, @antoniokov, great to hear! 🙂

---

<div class="post-metadata">

### 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: [April 29, 2025, 11:15am UTC](https://community.fibery.io/t/more-granular-rights-or-adjusted-rights/6096/4 "2025-04-29T11:15:29Z")

</div>


