Records in sys_security_acl_role hold sys_id instead of role name when grouped by roleSummaryWhen we navigate to the sys_security_acl_role and group them by role, we can see that some records are grouped by sys_id. This is because, there are certain ACLs which come along with a a fresh ServiceNow instance, and the roles are dependent on specific plugins or applications. One such ACL role sys_id is : b05940500a0a0aa70090a4893f6ff35d The list of ACL role records can be checked here - https://instance_name.service-now.com/sys_security_acl_role_list.do?sysparm_view=&sysparm_query=sys_user_role%3Db05940500a0a0aa70090a4893f6ff35d&sysparm_fixed_query=Related LinksThis sys_id belongs to the 'nobody' role. The 'nobody' role canot be viewed as admin or security admin. The role can only be viewed as 'maint' users or ServiceNow Personnels.