Commit error in update set when trying to add table level ACLsDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Update set commit encounters the following error when trying to bring an ACL: Skipping ACL Update: sys_security_acl_<sys_id> for table<table_name> as this instance runs in default allow mode and there are no other table level ACL's for table: <table_name>." Cause System property glide.sm.default_mode set to allow. Resolution One can create the ACL via UI /GUI manually. Additional Information The system property glide.sm.default_mode is set to deny by default in all new instances. No one can change this setting. Some old few instances have this set to allow. This will only occur for those few instances where the property is set to allow. Here's documentation regarding this property: https://docs.servicenow.com/csh?topicname=c_DefaultDenyProperty.html&version=latest It states that when the property glide.sm.default_mode is set to value "allow": Allow Access: The wildcard table ACL rules allow the read, write, create, and delete operations on all tables unless there are specific table ACL rules in place to restrict such operations.