[DONE] 'Locking' entities

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 unlocked by a manager).

For me, it actually relates to role-dependent https://community.fibery.io/t/entity-level-permissions/117/9?u=chr1sg
In the perfect world, the lock list and the unlock lists would be dynamically determined (maybe based on fields already available in the entity).

2 Likes

Agree with this, +1. Actually a feature of Notion that I really like. I’ve had my team too often inadvertently
delete/edit something that was a headache to undo.

It’s worth noting that you guys here in Fibery already have the great capability for only the Admin to set up fields and options, for example in Dropdowns. I used to have in Jira people put in “labels” that would be a real pain, and in the case of Jira and many other apps, it’s very hard to undo when any user adds one.

For example, I’d have these two labels:

“Label” and
“label”

since they were case sensitive.

Thanks guys!

This would be very useful at the field level too - especially for relationships. I have a lot of entities that are named with a formula based on a linked entity (that’s automatically generated). So there’s never a need to unlink. It would be great to be able to lock that field so people don’t accidentally unlink and then lost the context.

3 Likes

I would have thought entity level permissions would cover this but I am now not sure. We can share a more restrictive layer of permissions with a user but it doesn’t look like that revokes their access if they already have a greater level of access for another reason

Released today