Enabling access to protected scope applications for AI Data Explorer and Query Generation

  • Release version: Zurich
  • Updated March 30, 2026
  • 1 minute to read
  • AI Data Explorer and Query Generation require additional security configuration to access tables in protected scopes such as Human Resources or Employee Profile scopes.

    Protected scopes in ServiceNow restrict access to sensitive data, ensuring that only authorized users can view or interact with specific tables. When AI Data Explorer and Query Generation attempt to access tables within these protected scopes, additional security measures must be configured to enable proper functionality.

    Outside of protected scopes, AI Data Explorer and Query Generation use standard Access Control Lists (ACLs) shipped with the plugin. These ACLs are sufficient for unprotected scopes where normal security rules apply. However, protected scopes introduce additional restrictions that help prevent even administrators from accessing certain data without explicit authorization.

    When a table is linked to a protected scope, the scope takes ownership of security decisions for that table. This means that the standard ACLs shipped with AI Data Explorer and Query Generation are no longer sufficient. The protected scope requires its own set of ACLs that mirror the functionality that the plugin’s standard ACLs provide.

    Additionally, when Query Generation attempts to fetch data from protected scope tables through API calls, the system creates Restricted Caller Access (RCA) records. These records must be approved by administrators with appropriate scope permissions before the data access can proceed. This approval process ensures that cross-scope data access is explicitly authorized and monitored.

    Without proper ACL configuration, users cannot create or read records in AI Data Explorer for protected scope tables. Without approved RCA records, Query Generation cannot fetch data or generate insights for protected scope tables, resulting in error messages and limited functionality.

    The security configuration process involves two main components: creating scope-specific ACLs that call a public script include provided by the AI Data Explorer plugin, and approving RCA records that enable Query Generation to access protected scope data through API calls. Both components are necessary for full functionality with protected scopes.