Permissions for Field-Level Access Control in Freedom UI (to restrict certain fields of a record to be edited only by a specific Role)

Hello everyone,

I am trying to implement a permissions model for a collaborative application in Freedom UI, where different users interact with a record based on their role as explained below -

1. Author – The user who creates the record.
   • Can create new records.
   • Can edit all fields of the records they created, except some restricted fields.
2. Reviewer – A special role that:
   • Can view all records
   • Can edit only specific fields like:
     • Review Comments (this field can only be modified by the Reviewer and not by the Author)
   • Cannot modify other fields (e.g., Title, Description).
3. All other employees:
   • Can create new records (and thereby become a new Author).
   • Can view records created by others (including the fields updated by the Reviewer) but cannot edit other’s records.

 What I have tried so far

1. Object Permissions:
   • Enabled Object-level permissions on the entity.

   • Gave All Employees role: Create and Read rights.

     

      

2. Column Permissions:

   • For restricted fields (Reviewer Comments), :
     • Gave “Permit Reading and Editing” permission to the Reviewer role

     • Gave “Permit Reading” to All Employees

       

    

3. Record-Level Access via BPM:
   • Created a business process that:
     • Triggers when a record is created.
     • Reads the CreatedBy user.
     • Assigns Read and Edit rights using "Change Access Rights" → “For an employee”.

   • This was intended to ensure that Authors can edit their own records.

     

But the current outcome is that while users can create records successfully, they are unable to edit their own records afterward due to lack of permission.

Would appreciate any help on why the Authors are not able to update their own record.  I hope this is a valid scenario supported by Creatio. 

Also, this whole process seems to be a bit tedious. Is there a simpler way to achieve this using the no-code approach (without going into JavaScript coding to set the visible property based on roles)?

Thanks in advance for any insights!

Ajay