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
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?
What if you are an editor and want to not be able to edit the view?
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.
1 Like
This is correct
1 Like
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.
1 Like
Are you the admin?
If so, perhaps this is something that you would appreciate:
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.
3 Likes
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
1 Like
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
While it’s great to be able to recover information, at the end of the day, prevention is better than a cure.
Do you mean making certain fields read-only (for some users)? Or do you mean preventing fields from being configured/deleted (by some users)?
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.
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:
1 Like