# \[DONE\] Option to lock documents like Notion so that no information will be deleted by accident **URL:** \ **Category:** Ideas & Features\ **Tags:** rich-text\ **Created:** [April 11, 2023, 9:55am UTC](https://community.fibery.io/t/done-option-to-lock-documents-like-notion-so-that-no-information-will-be-deleted-by-accident/4296 "2023-04-11T09:55:18Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [April 11, 2023, 9:55am UTC](https://community.fibery.io/t/done-option-to-lock-documents-like-notion-so-that-no-information-will-be-deleted-by-accident/4296/1 "2023-04-11T09:55:18Z")
We often embed views in documents so that we can create an ‘Instructions & settings’ document per workspace. It would be great if we have an option to ‘Lock the page’ (like Notion). ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/349258146170d0c56b798b359e3cefc0e71009d9.png) In that way the document information and views can’t be deleted by accident. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f19351ae2bcbd6b8e61f7386bffc43c0a7605163.png) Context: the main user is also the admin; since we set up the whole workspace, they are not used to Fibery’s features. We create views to embed in documents, but hide those views so that the left menu as clean and short as possible. This will also be really helpful if we build our whole Wiki in Fibery. As a creator it feels safe if you can lock a document so you can’t mess it up by accident. **Edit** Off course user should be able to change the settings. Don’t know if it’s technically possible what I’m asking. But it would be awesome that they can’t change the information on a document (text + embedded view) but can change the data in that view. ---
**Author:** ![Aleksey\_Adamovich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aleksey_adamovich/32/6591_2.png) [@Aleksey\_Adamovich](https://community.fibery.io/u/Aleksey_Adamovich)\ **Post date:** [April 12, 2023, 6:47pm UTC](https://community.fibery.io/t/done-option-to-lock-documents-like-notion-so-that-no-information-will-be-deleted-by-accident/4296/2 "2023-04-12T18:47:20Z")
I see the team is currently working on “entity-level access”. > [@\[DONE\] Entity-level permissions](https://community.fibery.io/t/in-dev-entity-level-permissions/2163): > > Why? So far all the [access management](https://help.fibery.io/en/articles/5350066-permissions) in Fibery happens on the App level. The only way to share an individual Entity (ex. a Task) with a teammate is via read-only [external sharing](https://help.fibery.io/en/articles/5303654-sharing-entities-and-documents) poop Introducing Entity-level permissions will unlock new opportunities: Collaborating with clients As we’ve learned, Fibery is a surprisingly good fit for many service companies: think digital agencies and development studios. A good fit, that is to say, before we start talking about access management. … At least you will be able to prevent other users from editing. And probably after the release of that feature, it will be easier for Fibery to release also your idea to lock your own entities. ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [April 12, 2023, 8:00pm UTC](https://community.fibery.io/t/done-option-to-lock-documents-like-notion-so-that-no-information-will-be-deleted-by-accident/4296/3 "2023-04-12T20:00:23Z")
> [@Aleksey\_Adamovich](#): > > At least you will be able to prevent other users from editing. That’s not a solution for my customers unfortunately. Since they are solopreneurs and therefor admin of the space 🥲 ---
**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:** [April 12, 2023, 8:04pm UTC](https://community.fibery.io/t/done-option-to-lock-documents-like-notion-so-that-no-information-will-be-deleted-by-accident/4296/4 "2023-04-12T20:04:00Z")
Would implementation of [this](https://community.fibery.io/t/non-admin-mode-for-admin-0/2086) help? ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [April 13, 2023, 8:38am UTC](https://community.fibery.io/t/done-option-to-lock-documents-like-notion-so-that-no-information-will-be-deleted-by-accident/4296/5 "2023-04-13T08:38:56Z")
Yes, that would really helpful since I don’t want our users to be admin 😅 That will prevent a shitload of problems. Although for this specific use case I’m in doubt. - If you are a ‘creator’ → you need to be able to create documents and change them. - As a creator it’s still a very useful feature to lock documents so that you can’t fuck them up by accident. - So without that option, it’s still not very clear for me how a creator **can** create documents in a space, but **can’t** change documents that ideally don’t need to be changed (for example: the documents that we’ve made in that space (that act as a “folder / wiki / read me” page). Or will it be possible with the new permission model that you will have permissions per document? That would be really helpful. But even then it’s really nice for a creator to lock a document when you’re done 🙂 ---
**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:** [April 13, 2023, 8:59am UTC](https://community.fibery.io/t/done-option-to-lock-documents-like-notion-so-that-no-information-will-be-deleted-by-accident/4296/6 "2023-04-13T08:59:02Z")
> [@YvetteLans](#): > > it’s still not very clear for me how a creator **can** create documents in a space, but **can’t** change documents that ideally don’t need to be changed Well, I suspect that we will never implement a solution that makes a document (or an entity) permanently read-only for all users, so I would imagine any solution would always allow for someone with the appropriate privilege level to be able to re-open a locked document. But I guess there is a valid use case for making inadvertent changes less likely. Side note: if you wanted to create a database of _entities_ that are 100% read-only, this is technically possible by making a custom integration which syncs external data into Fibery, whereby the data is read-only from the point of view of the Fibery workspace. ---
**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\ **Post date:** [April 13, 2023, 9:08am UTC](https://community.fibery.io/t/done-option-to-lock-documents-like-notion-so-that-no-information-will-be-deleted-by-accident/4296/7 "2023-04-13T09:08:21Z")
@YvetteLans - That would indeed be very useful if the new permission model would allow permissions to be set per document, which I belief is exactly what it does! 😊 ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [April 13, 2023, 9:29am UTC](https://community.fibery.io/t/done-option-to-lock-documents-like-notion-so-that-no-information-will-be-deleted-by-accident/4296/8 "2023-04-13T09:29:39Z")
> [@Chr1sG](#): > > so I would imagine any solution would always allow for someone with the appropriate privilege level to be able to re-open a locked document. Off course! The goal of ‘locking a document’ is not that no one else can unlock or change it 🙂 It should work like Notion; everyone with permissions in that document can unlock and change the document. So our clients can ruin something by accident; we can live with that! 😄 But it would be great if we can make it quite hard for them. I used the ‘lock’ option in Notion all the time so I can’t put a typo or delete by accident while opening the page for example. ---
**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:** [April 13, 2023, 9:45am UTC](https://community.fibery.io/t/done-option-to-lock-documents-like-notion-so-that-no-information-will-be-deleted-by-accident/4296/9 "2023-04-13T09:45:04Z")
I’m going to link a couple of related topics here, just for visibility > [@Lock Views from Editing](https://community.fibery.io/t/lock-views-from-editing/3138): > > 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 > [@'Locking' entities](https://community.fibery.io/t/locking-entities/911): > > Would it be possible to make it so that an entity can be locked for changes (and unlocked again when needed)? It’s sort of a permissions issue, but I need the permissions to be dynamic, rather than fixed by the admin at app level For my use case, simply switching the entity between ‘apply-normal-permissions’ and ‘nobody-can-edit’ is what I need. Depending on the implementation, the users who have lock/unlock permissions could be asymmetric (an engineer can lock an entity but it can only be unl… ---
**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:04pm UTC](https://community.fibery.io/t/done-option-to-lock-documents-like-notion-so-that-no-information-will-be-deleted-by-accident/4296/10 "2024-12-19T15:04:39Z")
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 … ---
**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, 3:15pm UTC](https://community.fibery.io/t/done-option-to-lock-documents-like-notion-so-that-no-information-will-be-deleted-by-accident/4296/11 "2024-12-19T15:15:12Z")