# \[DONE\] Lock Views from Editing

**URL:** <https://community.fibery.io/t/done-lock-views-from-editing/3138>\
**Category:** Ideas & Features\
**Created:** [August 2, 2022, 11:43pm UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138 "2022-08-02T23:43:36Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [August 2, 2022, 11:43pm UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/1 "2022-08-02T23:43:36Z")

</div>

Now that I’ve shared a Fibery Space with the company/client it would be nice to lock certain views. Locking should make all modifications either a) impossible or b) personal.  
It would be great to restrict editing to certain users

---

<div class="post-metadata">

**Author:** ![Anton\_Oparienko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/anton_oparienko/32/5342_2.png) [@Anton\_Oparienko](https://community.fibery.io/u/Anton_Oparienko)\
**Post date:** [August 3, 2022, 8:11am UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/2 "2022-08-03T08:11:16Z")

</div>

Hi! May be I don’t understand the case completely or what should be possible/restricted but doesn’t editor/contributer roles do exactly that - restrict editing of views, potentially restrict editing entities?

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [August 4, 2022, 3:11am UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/3 "2022-08-04T03:11:13Z")

</div>

What if you are an editor and want to not be able to edit the view?

---

<div class="post-metadata">

**Author:** ![Anton\_Oparienko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/anton_oparienko/32/5342_2.png) [@Anton\_Oparienko](https://community.fibery.io/u/Anton_Oparienko)\
**Post date:** [August 4, 2022, 8:27am UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/4 "2022-08-04T08:27:38Z")

</div>

From my experience Editor can’t edit or create new views (apart from documents and whiteboards), can only do “My filters” on top of global filter. Can’t change rows, columns, fields etc.  
Only starting from “Creator” role you are able to configure the space and the views.  
Please, correct me if i’m wrong somewhere.

---

<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:** [August 4, 2022, 12:11pm UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/5 "2022-08-04T12:11:33Z")

</div>

> [@Anton\_Oparienko](#):
>
> From my experience Editor can’t edit or create new views (apart from documents and whiteboards), can only do “My filters” on top of global filter. Can’t change rows, columns, fields etc.  
> Only starting from “Creator” role you are able to configure the space and the views.

This is correct

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [August 23, 2022, 2:11pm UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/6 "2022-08-23T14:11:15Z")

</div>

Thank you for the correction in terminology.

I’m the creator and always in creator mode. It’d be great to lock vies from editing.

---

<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:** [August 23, 2022, 2:55pm UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/7 "2022-08-23T14:55:25Z")

</div>

> [@helloitse](#):
>
> I’m the creator and always in creator mode

Are you the admin?  
If so, perhaps this is something that you would appreciate:

> [@"Non-admin" mode for admin :0)](https://community.fibery.io/t/non-admin-mode-for-admin-0/2086):
>
> In short: The ability to switch to a mode in which all settings (links) available to administrators are not visible. Why: In day-to-day work in a “flow” state, all these unnecessary links (apps, buttons, menu items) are very distracting. Excessive cognitive load. Solution options: The solution is generally universal and most likely has already been discussed on the forum. A set of pre-configured interface types, with the ability to switch between them. As an example, how this is implemente…

Then you could flip between having configuration capabilities and just having ‘normal’ user capabilities.

Until that is available, you could have two accounts, each with different permissions, and switch between them.

Otherwise, you will need to ask the admin to downgrade you from creator level.

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [September 8, 2022, 6:37pm UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/8 "2022-09-08T18:37:34Z")

</div>

I definitely think this feature request meets the need!  
I’d add the details that I wouldn’t ever see switching profiles as a solution for my use case.  
I often have one or two apps that are in great condition and never need tweaking, but I’m building apps, databases, and views for my clients. So I bounce between apps and views. I may work in a view that requires no configuration and then 5 minutes later, I need to create a new view and make changes to it.  
I’d be better to toggle this on and off per app/database

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [January 6, 2023, 8:47pm UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/9 "2023-01-06T20:47:39Z")

</div>

I think this feature should be expanded to include locking field configuration as well as views.  
I was just working with a user case for the locking functionality that cannot be solved by multiple users.  
When practicing view configuration with a new user, the user has to be an editor/admin. However, it would be prudent to lock essential fields that are core to the data model and should never be edited/deleted.

I think this is core to the “Fear Management” @B_Sp mentions here: [[DONE] Undelete Fields / In Audit Log, keep activity in Deleted fields](https://community.fibery.io/t/done-undelete-fields-in-audit-log-keep-activity-in-deleted-fields/1777)

While it’s great to be able to recover information, at the end of the day, prevention is better than a cure.

---

<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:** [January 7, 2023, 10:38am UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/10 "2023-01-07T10:38:01Z")

</div>

> [@helloitse](#):
>
> it would be prudent to lock essential fields that are core to the data model and should never be edited/deleted.

Do you mean making certain fields read-only (for some users)? Or do you mean preventing fields from being configured/deleted (by some users)?

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [January 12, 2024, 4:19pm UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/11 "2024-01-12T16:19:16Z")

</div>

I mean preventing fields from being configured/deleted by some or most users.  
In my example the focus is on the fields configuration, not daily use

> the data model and should never be edited/deleted.

It’s possible to want a user to be able to use a dropdown but not to be able to change the options, or to be able to configure views in an app, but not be able to delete fields core to the data model.

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [January 17, 2024, 9:02pm UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/12 "2024-01-17T21:02:37Z")

</div>

I just realized there is a different feature request for this that I’ve apparently liked some time ago. Adding here for any interested parties:

> [@Locking apps for change](https://community.fibery.io/t/locking-apps-for-change/809):
>
> There comes a time when an app is pretty much fixed - it might evolve but it is more about usage than creation. When I’m a bit tired, sometimes I reach for the ellipsis in a related entity and I intend to hit “Unlink relation” but sometimes I accidentally hit the ellipsis above and absent-mindedly hit “Delete relation”. There is a warning box but we all know about modal errors and tired brains. Would it be possible for creators to put Apps into a “locked” state from their Types view - sort of l…

---

<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:** [December 19, 2024, 3:03pm UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/13 "2024-12-19T15:03:16Z")

</div>

Released today

> [@December 19, 2024 / Lock Views & Documents, Quick filter items in Sidebar, Faster Search (santa last release of the year)](https://community.fibery.io/t/december-19-2024-lock-views-documents-quick-filter-items-in-sidebar-faster-search-last-release-of-the-year/7993):
>
> This is the last release of the year sweat_smile. 2024 was a very productive year for our development team, and I think we’ve reached our productivity plateau with 450 features released. There are 52 weeks in 2024 and we shipped 51 releases. I hope you like Thursdays as we do. It is sometimes stressful, but it’s also very rewarding to bring more value and make Fibery better every week. 2021 2022 2023 2024 -- -- -- -- Releases …

---

<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:** [December 19, 2024, 6:05pm UTC](https://community.fibery.io/t/done-lock-views-from-editing/3138/14 "2024-12-19T18:05:29Z")

</div>


