When upgrading, a sysevent_script_action.* Read ACL is automatically created with required role 'maint'<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue When upgrading to Yokohama, a read acl with required role = 'maint' is created for sysevent_script_action is automatically created, preventing even admin users from viewing records. Symptoms System property 'com.glide.security.strict_read_roles' is trueACL is created by 'system' Release Yokohama Cause When 'com.glide.security.strict_read_roles' is true, wildcard ACLs are automatically created where field-level read ACLs exist. This is legacy behaviour. The current recommendation is to set 'com.glide.security.strict_read_roles' to false, but it is not automatically set on existing instances. For details, see: KB1204813 Resolution Set com.glide.security.strict_read_roles to false (confirm there are no unexpected impacts in a sub-prod environment)Create a new sysevent_script_action.* read ACL with required role = admin