Hi Team,
I need to grant users the ability to create and edit entities, but prevent them from deleting, merging or converting to any entity. This permission granularity is essential for our workflow because i have no control if any of my team delete, merge or convert to (by mistake or no) any entity…
Thanks in advance!!
1 Like
Hey Fede! Welcome!
There’s a workaround you do for now if it’s urgent, but it’s not the prettiest, and you need to be on the pro plan.
Instead of giving access via the space/database, you just give view access to the space, and submitter access to all databases, then access via Custom Access Templates.
So you create a database called “Organization” then make sure to relate all other databases to the organization. Then add a People Field with automatic access to a custom access template where they can edit, but not delete. You just need to remember to configure the access template any time you add a new database, but that shouldn’t be too often once you have it all set up.
It’s not the cleanest solution, and I also advocate for more granular access control (like access templates) for space and database access, but it feels like the Fibery team is reluctant to implement this as it’s less user friendly. But until then, this should work.
Lmk if anything doesn’t make sense!