Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Non-admin users do not see the wrong scope message for records not in currently selected application scope - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Non-admin users do not see the wrong scope message for records not in currently selected application scope
KB0823213

Non-admin users do not see the wrong scope message for records not in currently selected application scope


1010 Views Last updated : May 15, 2024 public Copy Permalink
KB Summary by Now Assist

Description

Non admin users do not see cross scope update warning messages like;
This record is in the Global application, but {{application}} is the current application. To edit this record click here.

Only a user with the admin role will get this type of message.

As a result updates may not end up an the expected Update set.

Steps to Reproduce

A scoped admin user (role like x_myscope.admin), who is for example catalog_editor could be in the applications scope context.

From there open a catalog item from the global scope, but not get the message.

Workaround

There is no workaround other than granting the user the global admin role.

Users with low level roles do not have the same concept of scoping (and can not choose a scope) so data is not separated the same way.


Related Problem: PRB1388380

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.