# Allow editing of views

**URL:** <https://community.fibery.io/t/allow-editing-of-views/9945>\
**Category:** Ideas & Features\
**Created:** [November 3, 2025, 3:03pm UTC](https://community.fibery.io/t/allow-editing-of-views/9945 "2025-11-03T15:03:37Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [November 3, 2025, 6:31pm UTC](https://community.fibery.io/t/allow-editing-of-views/9945/3 "2025-11-03T18:31:00Z")

</div>

We already have plans to make it possible for someone’s access to the views in a space being separated from their access to the data in the databases in the space.  
However, the plan is that the rights to configure/see a view will still be covered under the umbrella-level of the space access. In other words, you will be able to make someone an architect in a space, and not extend that to making them owners for all the data in that space. But you won’t be able to control access on a view by view basis - it will be all or nothing for the views in a space.

> [@Wilco\_Boode](#):
>
> It would be nice if this can be arranged more easily, linking it either to database access, or making it an “editable by” thing.

We have no plans to make the ability to configure a view dependent on a person’s access to the database used in the view.

---

_[View the full topic](https://community.fibery.io/t/allow-editing-of-views/9945)._
