Users with "sn_cmdb_admin" can edit the Asset field on cmdb_ci table

[SD_Akshay]

Hello All,

I have created write ACL with role mentioned with field and table for the above requirement, but even after implementing and adding the ACL the field still shows as read only for that user role. 

The field is OOB read only active true and with attribute readonly_clickthrough=true.

Please tell me if anything needs to change or any other configuration needs to apply

[Tanushree Maiti]

Once it is open to everyone, you need to control the edit control by write  ACL (Field level ACL) on field "ci" on alm_asset table mentioning the specific role 

[rameshperab]

Hi Akshay,

I think the issue is not with your ACL here. Since you mentioned the field is OOB read only and also has the attribute readonly_clickthrough set to true, that is most likely the reason why it is still not editable.

In ServiceNow, even if the ACL is correctly giving write access, the field can still appear read only if it is enforced at the dictionary or UI level. So in this case, the read only setting is overriding your ACL.

For testing, you can try the following:

• Temporarily remove the Read only setting from the dictionary
• Remove the readonly_clickthrough attribute
• Also check if any UI Policy or Client Script is making it read only

Once you remove the read only restriction, your ACL should start working as expected.

If this helps, please consider marking it as Helpful or Accept as Solution

[rameshperab]

Hi Akshay,

From your description, it looks like the issue is not with the ACL but with how the field is configured.

Since the field is OOB read only and has the attribute readonly_clickthrough set to true, it will remain read only at the UI level even if the write ACL is correctly configured for the role.

In ServiceNow, ACL controls permission, but dictionary settings and UI configurations (like read only fields, UI policies, or client scripts) can override and still prevent editing.

Additionally, since the Asset field is a reference field, you may also want to check if it is being controlled by reference or if there is any configuration on related tables like alm_hardware that is enforcing read only behavior.

For testing, you can try the following:

• Remove the read only setting from the dictionary temporarily
• Remove the readonly_clickthrough attribute
• Check for any UI Policy or Client Script making the field read only
• Verify if there is any reference-level control or related table configuration affecting it

Once the read only restriction is removed, your ACL should work as expected.

If this helps, please mark it as Helpful or Accept as Solution 

[Ankur Bawiskar]

@SD_Akshay 

what's your business requirement?

Even if you create field level WRITE ACL you need to check if the field is readonly at dictionary level

Any client script or UI policy is making it readonly?

what debugging did you do?