In the new editor we can now set view/edit permissions on individual fields.
My question: when a field is set so that only admins can view and edit it, why isn’t that field hidden by default from the table views for all other users? At the moment it still shows up in the tables no matter the user role and has to be removed from each view manually.
If a user doesn’t have view permission on a field, it seems logical that the field simply shouldn’t appear in tables for them — otherwise the permission setting and the view configuration have to be maintained separately.
Is this intentional behaviour, or is automatic hiding something that’s planned?
You’re absolutely right. This is something we still need to enforce consistently, including in the record activities. It’s part of the finishing work for the new Record Experience.
We had to introduce Field Access relatively early because it affects so many different parts of Tape. The remaining enforcement will be rolled out as part of moving the new record out of beta and eventually switching off the old record.
Strictly speaking, we would also need to hide those fields in the corresponding places in the classic record. We haven’t touched that yet because we’re waiting for the broader rollout of the new experience rather than building the same behavior twice.
So yes, you identified this correctly. Fields that a user doesn’t have access to should of course be handled accordingly in table views as well.