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 (i.e HR or 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.

Resolution

• 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.
• 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 any additional roles to the ServiceNow service account that allows it to access components from this non-global scope (i.e an 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"

If you are still having difficulty please reach out to us: https://support.glean.com.