Already a NinjaOne customer? Log in to view more guides and the latest updates.

NinjaOne Integration with ServiceNow: Troubleshooting Error for Cross-Scope Access Policy

  • Last Updated October 26, 2026

Issue

The ServiceNow integration in NinjaOne returns the following error: "Write operation against 'oauth_entity' from scope 'x_nrmm_ninjaone_in' has been refused due to the table's cross-scope access policy."

Environment

  • NinjaOne Integrations
  • ServiceNow

Cause

This error occurs when the user has some access policies in their instance. 

Servicenow_cross scope access error.png
Figure 1: Example of a cross-scope access policy error in ServiceNow

Resolution

The workaround to solve this issue is to manually update the URL in the Application Registry. To do so, perform the following steps: 

  1. On the NinjaOne Configuration Settings page in ServiceNow, open the application registry in the Outbound OAuth Registry tab. 
servicenow_configuration_outbound oauth.png
Figure 2: Access the outbound OAuth registry for NinjaOne configuration
  1. Edit the record and review the Token URL field. Ensure that your NinjaOne instance is included at the beginning of the address. To obtain the data for your instance, find the value in the URL bar between https:// and ninjarmm.com. 
servicenow_valid token url.png
Figure 3: Example of a valid token URL

Additional Resources

Our ServiceNow integration documentation in NinjaOne will help you get the most out of NinjaOne's integration with ServiceNow.

For an outline of all integration resources, refer to Integrations and Third-Party Apps: Resource Catalog.

FAQ

Next Steps