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?

[MrMuhammad]

Hi @Syn Core,

Is this resolved or do we need a follow-up on this? If resolved, please close the thread by marking the response as correct to benefit future users. 

if you have any further questions please do let me know. 

Regards,

Muhammad

[zuz_zuz_zuz]

Is this "update, not copy" recommendation still valid? I've always heard to not update OOTB records 😕

[Mark Manders]

Please mark Muhammad's answer as correct, since this is best practice. It used to be the other way around, but for maintenance purposes changing the OOB objects (including ACL's) is the better way to go. On patching and upgrading you will have some more work to do when checking the skipped changes, but at least you're in control.

If my answer helped you in any way, please then mark it as helpful.

Mark