# 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:** 6

<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, 7:04pm UTC](https://community.fibery.io/t/allow-editing-of-views/9945/6 "2025-11-03T19:04:50Z")

</div>

> [@RonMakesSystems](#):
>
> If you do not extend to databases, does the architect have the ability to create new databases?

That is the plan, yes.

I realise now that the upcoming feature may not deliver on [this request](https://community.fibery.io/t/separate-the-view-config-access-and-data-config-access/9067).

Here’s a mockup of (which uses the outdated `Creator` terminology, but) which is indicative of where we’re probably heading.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/cba0a974b25304db08095c04bb43ff73fe998e17.jpeg)

When making someone an space `Architect’, you can choose whether to extend this to all of the data in the databases in the space.  
An (unextended) Architect will be able to create/configure views and databases in the Space, but not see/manipulate any data (unless specifically granted access by some other means).

---

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