It would be nice to have fine grained permissions on field/table level.
e.g. when you manage employees, you don’t want everybody to see also the salary information.
It would be nice to have fine grained permissions on field/table level.
e.g. when you manage employees, you don’t want everybody to see also the salary information.
Hello @mwesox! First of all, welcome to Baserow 
Role-based access control is planned for Baserow 1.13, stay tuned!
@olgatrykush
I’ve been exploring the RBAC features and found that the filed level permission locks the whole column, including data entry.
Is there a way to just lock the “edit field” menu?
The idea is that in a large team scenario - there are usually users who should be able to enter data, but not change the field settings
(like adding a single select option, or change the field type).
I have to admit that this is one of the key features my team used in Airtable. It surely makes managers’ lives less stressful ![]()
If it’s not possible yet, have you considered adding such a feature?
Hey @dev-rd, we don’t have field-level permissions yet. Currently, we support permissions at the workspace, database, and table levels, and view-level permissions are in development. Am I missing anything?
@olgatrykush I meant this:
but with more control
Oh, got it. In that case, you can define the editor roles at the table level, and those users will be able to edit the field:
Field-level permissions are a way to refine the access a user already has at the table level; they do not replace table permissions. Field permissions can only restrict editing further; they can’t grant editing to roles that can’t edit the table.
I’m an editor here and can add/modify data, but I can’t edit the field settings:
Is it what you’re looking for?
I can work with that. Thanks!