# \[DONE\] Locking apps for change

**URL:** <https://community.fibery.io/t/done-locking-apps-for-change/809>\
**Category:** Ideas & Features\
**Created:** [June 30, 2020, 3:35pm UTC](https://community.fibery.io/t/done-locking-apps-for-change/809 "2020-06-30T15:35:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChrisSparkT](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chrissparkt/32/597_2.png) [@ChrisSparkT](https://community.fibery.io/u/ChrisSparkT)\
**Post date:** [June 30, 2020, 3:35pm UTC](https://community.fibery.io/t/done-locking-apps-for-change/809/1 "2020-06-30T15:35:50Z")

</div>

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 like a production state. While it is checked it isn’t possible for creators to accidentally mess things up. If creators want to go and truly delete relations (for example) they would need to uncheck the state from the Types view and go into a development mindset from a use mindset.

---

<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 3, 2026, 4:57pm UTC](https://community.fibery.io/t/done-locking-apps-for-change/809/2 "2026-01-03T16:57:05Z")

</div>

I think this need is addressed by the [[IN DEV] "Non-admin" mode for admin - #5 by a2say](https://community.fibery.io/t/in-dev-non-admin-mode-for-admin/2086/5) feature currently in development.

---

<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:** [January 22, 2026, 3:46pm UTC](https://community.fibery.io/t/done-locking-apps-for-change/809/3 "2026-01-22T15:46:26Z")

</div>

Fixed in latest release

> [@January 22, 2026 / 🎛️ Architect mode, many AI and validation rules improvements](https://community.fibery.io/t/january-22-2026-architect-mode-many-ai-and-validation-rules-improvements/10284):
>
> control_knobs Architect vs. User modes Today we’re introducing a new way to keep Fibery calm and safe for everyday work: Architect vs. User modes. Admins and Architects can now switch between two modes: User mode: a cleaner, focused interface for daily work. Advanced controls are hidden: no accidental field edits, no surprise layout changes, fewer dangerous actions like Delete Relation Field in your face. Architect mode: the full power view for workspace design. Architect mode can be …