REST Aggregate API returns "Insufficient rights to query records" for kb related tablesIssue <!-- 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; } --> The Aggregate API (api/now/stats/{table_name}) returns the below response even though the user has access to these records from the list view. { "error": { "detail": "No permission to read table 'kb_knowledge'", "message": "Insufficient rights to query records" }, "status": "failure" } ReleaseThe PRB has been fixed in New York Patch 8 and higher, Orlando Patch 2 and higher, and all family versions from Paris and higher.CauseThis is a known error reported in PRB1332230.ResolutionTo workaround this issue, you need create a table level read ACL for the affected table. For the kb_knowledge as an example, follow the below steps. Login as admin.Elevate roles to security_admin.Go to sys_security_acl.list from the filter navigator. Click on 'New' to create a new ACL.Set the values as below: Type: recordOperation: readFor the name, select kb_knowledge from the tables dropdown menu and 'None' from the fields dropdown menu.Under 'Required roles' list, add 'itil' role or the role that the affected users have. Save the record.