Is it better to create a new ACL than to update an OOB ACL

[Syn Core]

I have been task with creating new roles and ACL's on a couple OOB tables. I want to know if it is better to use create a new ACL at a field level or to use one that is OOB.

For example, on the Change Request table I need the user to have write ability to the short description and description field and I noticed that there is already and OOB field level for short description and description. Should I use the OOB ones and add my new role or create a new one for my new role?

[PrashantLearnIT]

Hi Syn,

Create a new ACL for your new role, that should be a good way of doing it.

Please Mark my answer correct & helpful.

Thanks,

Prashant

[Dazler]

So you are suggesting that I create a new field level for both the short description and description?

[PrashantLearnIT]

Yes

[MrMuhammad · Accepted solution]

Hi @Syn Core ,

It is recommended to update the existing OOB ACL. As per Servicenow customization best practices update objects in place wherever possible, except for Service Portal widgets and other items designed to be reused. 

Source: What are the best practices for customization? | Customer Success Center

ACLs are not reusable so updating the existing one will be easy to maintain.

Please mark this helpful/correct, if applicable.

Regards,

Muhammad