Unable to make fields non-editable on Compliance workspace

[Kartik Magadum]

Hi,
I've set up a 'list_view' ACL which is functioning correctly in the Native UI, but it's not taking effect in the Compliance Workspace.

1. ACL :

2: Workspace: Fields are editable. 

Thanks.!
Kartik Magadum

[Community Alums]

Hi @Kartik Magadum ,

Are there any other list_edit ACLs on these fields?

Don't use the lowest level roles (snc_internal) if you are restricting access to any data, use admin or some higher-level roles who have at least read access for the data.

In this ACL, you don't need any role as you are using script to provide access.

Regards

Anand

[Kartik Magadum]

Hi
Thanks for reply.

Are there any other list_edit ACLs on these fields? -- > No
In this ACL, you don't need any role as you are using script to provide access. -- > Role can't be empty if I'm not wrong. 

Thanks.!

[Community Alums]

Role can be empty.

Read warning info displayed while creating ACL.

A role, security attribute, data condition, script or ACL control via reference fields is required to properly secure access with this ACL.

Which workspace you are using? 

The screenshot you are sharing is not applied to list_edit ACL, it's a form view. List edit applied when you try to edit field by double clicking on field .

[GlideFather]

Hi @Kartik Magadum

most likely it is because of using the wildcard (*)

You have the record with sn_compliance_control.* and this rule is applied to ALL THE FIELDS THAT ARE NOT EXPLICITLY DEFINED

So please go to the list of ACL and check and review for all the records sn_compliance_control.<field_name>