# Unintuitive permissions for new users

**URL:** <https://community.fibery.io/t/unintuitive-permissions-for-new-users/8426>\
**Category:** Ideas & Features\
**Tags:** permissions\
**Created:** [March 11, 2025, 6:27pm UTC](https://community.fibery.io/t/unintuitive-permissions-for-new-users/8426 "2025-03-11T18:27:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [March 11, 2025, 6:27pm UTC](https://community.fibery.io/t/unintuitive-permissions-for-new-users/8426/1 "2025-03-11T18:27:28Z")

</div>

As promised, here’s the permissions video. I got off a call with someone today, trying to explain the Fibery permissions because it didn’t make sense to them. Then I realised how unintuitive this (really great and powerful feature) is to users who are not already in the Fibery ecosystem. This video explains it in the perspective of a new user. Made with love and desire for the best tool there can be. Hope it helps with the new improvements coming to permissions. Or maybe its everything you already know. In any case thought id share.

[![](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e21131f6c5c05fc6639692a61dd46e9a7d3b8ef1.jpeg "Fibery Permissions") ](https://www.youtube.com/watch?v=F62ahHdd3Yc)

---

<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:** [March 12, 2025, 6:01am UTC](https://community.fibery.io/t/unintuitive-permissions-for-new-users/8426/2 "2025-03-12T06:01:24Z")

</div>

Thank you for the quality feedback! That’s all fair points:

- Space → Database permissions inheritance is not explained well.
- It’s not clear access templates are defined on the Database level but are applied on the Entity level.
- The capability to create “child” Entities is expected in the access template but is, in fact, configured on the Database level.
- Automatic access via Fields applies on the Entity level but is managed on the Database level.

We have specific plans to address all of these except for maybe the last one. Let’s see if we succeed!

---

<div class="post-metadata">

**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\
**Post date:** [March 12, 2025, 8:02am UTC](https://community.fibery.io/t/unintuitive-permissions-for-new-users/8426/3 "2025-03-12T08:02:27Z")

</div>

Those are good points. I imagine it would be good to clarify where a window is showing that I “manage database-level access” rather than “view people’s access to this database”, or “manage Space-level access”, or “manage entity-level access”. For the “view” aspect, it is probably good to have a clear “access audit” representation for the different levels.

Similarly for the Access Templates, perhaps they could be called “Entity Access Templates” to clarify that these provide entity-level permissions and not database-level.

---

<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:** [July 3, 2025, 11:06am UTC](https://community.fibery.io/t/unintuitive-permissions-for-new-users/8426/4 "2025-07-03T11:06:54Z")

</div>

We’ve added a screen to see access better for space and database

> [@July 3, 2025 / Show all Users who have access to Database or Space, Whiteboard improvements](https://community.fibery.io/t/july-3-2025-show-all-users-who-have-access-to-database-or-space-whiteboard-improvements/9127):
>
> Enjoy this small release with some improvements here and there. fingerprint Show all Users who have access to a Database or Space Just like the Entity Access Audit, we now display a searchable and expandable list of all Users who have any level of access to Database or Space, along with their corresponding capabilities. To trace the origin of a particular User’s capabilities, simply expand their entry. Access Audit is read-only: it does not permit granting, modifying, or revoking access.