Default scope for all custom applications.

Default scope for all custom applications.

• A. Private
• B. Public
• C. Global
• D. Restricted

Answer: (A)

In ServiceNow, custom apps run in their own isolated scope, which controls visibility and access to the app’s components. The default for a new custom application is Private, meaning the app and its tables, scripts, and UI are accessible only to users who have explicit access to that app in Studio. This isolation protects development work from unintended interactions with other apps and helps avoid naming or data conflicts while you prototype and test. If you want others to use or install the app, you’d publish it to a broader audience, but until then it remains private. Public and Global are not used as the default for new custom apps—Public would expose the app widely, Global is reserved for core system scope, and Restricted isn’t the standard default for custom apps.

In ServiceNow, custom apps run in their own isolated scope, which controls visibility and access to the app’s components. The default for a new custom application is Private, meaning the app and its tables, scripts, and UI are accessible only to users who have explicit access to that app in Studio. This isolation protects development work from unintended interactions with other apps and helps avoid naming or data conflicts while you prototype and test.

If you want others to use or install the app, you’d publish it to a broader audience, but until then it remains private. Public and Global are not used as the default for new custom apps—Public would expose the app widely, Global is reserved for core system scope, and Restricted isn’t the standard default for custom apps.