@Dylan Hi you claim that the request to be able to make fields read only for the purposes of admission within automated processes, where manual field entries are not suitable … has been “Delivered” by implementing Roles/Permissions for access to field entry … I disagree.
First - it’s not the same thing. Restricting access to fields based upon roles/permissions is good and applicable when data and data entry should be available based upon a users profile. That is NOT the case here. If we are using HB Workflows and like to set values then there are NO users that should have access to modify, most likely users can see value (that is arbitary). In simple terms the field should be Read Only. It is a common concept in databasics schema.
Second - roles/permissions are available only for Enterprise customers, whilst the tools setting the values, such as Workflows, are available for Pro users. So there’s a mismatch of capabilities to price point.
Can you please address this?
Thank you