SERVICENOW_6

Issue

There exist some records in some of the tables (see the setup instructions for the complete list of tables) which we access that we don't have full access to. This is typically attributed to records outside of the global scope (for example, HR or the Employee Core Knowledge Base).
Since access is limited, this results in reduced scope of what gets crawled and limits our ability to grant accurate permissions.

One can reproduce the error by using the Rest API Explorer, impersonating the service account user (gleansearchuser), and querying each of the listed tables. If the response is empty, that indicates a table our service account user does not have full access to.
The error details list each table with mismatched counts. For each table, open the Read ACL records: link as a ServiceNow administrator to check whether a read ACL on the table or its fields hides records from the service account. If there's no link, review the table's read ACLs in System Security → Access Control (ACL).
Coordinate with the ServiceNow admin to see if cross-scope access is feasible to allow the globally-scope user to access non-global components.
Also consider adding roles that allow the ServiceNow service account to access components from this non-global scope. For example, the account may need the sn_hr_core.admin role for HR scopes.
If granting higher privileges is infeasible and you accept the ramifications of the issue above, you can bypass this check with checking "Ignore under permissioned access to tables"

For additional assistance, please contact Glean Support at https://support.glean.com