Cross Scope Access

[GregC7266961130]

I created Factors and Group Factors in the GRC: Advanced Risk scope. When moved to production, I only have Global scope access. I cannot modify or update the Factors. Should I create them in Global scope instead?

[Tanushree Maiti]

Its not needed.

Switch to the correct application scope
change the scope from Global → GRC: Advanced Risk

then try to update group factor.

[GregC7266961130]

The issue is in production there is no switching scope. The changes are minor and it would take too much time to go through Dev —> UAT —> Prod. 

[Vishnu-K]

Hi @GregC7266961130  ,

What's happening here is that the Factors and Group Factors you created are owned by the GRC: Advanced Risk scope (sn_risk_advanced). ServiceNow only allows records owned by a scoped application to be edited when your application picker is set to that same scope. Since you're on Global in Production, the platform is blocking edits by design , this is not a permissions issue, it's application scoping working as intended.

The fix is straightforward , use the application picker (gear icon at the top of the instance), switch your active scope to GRC: Advanced Risk, and then open and modify your Factor records. That's the supported way to edit records owned by a scoped app.

On your question about recreating them in Global scope  that's not recommended. Mixing GRC configuration between Global and the Advanced Risk scope will cause maintenance and upgrade issues down the road. Keep everything inside the GRC app scope and just use the scope switcher to manage it.

The cleaner long-term approach is to make changes in Dev, publish a new app version, and install it in Production rather than editing directly in Prod , but switching scope is the immediate fix for what you're seeing.

Application Scope concepts — https://docs.servicenow.com/en-US/bundle/sandiego-application-development/page/build/applications/co...

How to move Custom Scoped Applications between instances (KB0961293) — https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0961293

Cross-scope access privilege record — https://docs.servicenow.com/bundle/vancouver-application-development/page/build/applications/referen...

Hope this helps!

If it helped you please do mark it as helpful and accept the solution

Thanks,

Vishnu

[GregC7266961130]

The issue is in production there is no switching scope. The changes are minor and it would take too much time to go through Dev —> UAT —> Prod.