Need to know if ACL is the right approach

[Servicenow lear]

Greetings ALl,

We have a use case on CMDB CI for our some prime classess where in we want to restrict editing some fields for these classess (aix,windows server, linux, esx , switch, network,router, firewall,u[ps,printers,handheld,computers) .

Fields :  Owned by , support group , environment, managed by 

Use case : only members of support group are supposed to edit these

Logic : create individual field ACLS at child class  which are turning upto 100 ACLS  or do create field acls at Hardware level

[Weird · Accepted solution]

You can always just create an ACL on parent table since that logic will affect child tables.
For example an ACL on cmdb_ci will apply to cmdb_ci_computer as long as there's no similar ACL on cmdb_ci_computer.

On cmdb_ci level you can just check the class of the current record in a condition to apply your logic so that it won't affect any other CI classes.