Skip to content
IT Canvass
Development · Lesson

Application scoping

Quick answer

Scoped applications are how you package custom development so it is isolated, portable and safe. Every scoped app has its own namespace (like x_acme_travel), its own tables and files, and explicit rules about what it may touch outside itself. This is the modern default, the opposite of dumping everything in the Global scope.

Key takeaways

  • Why scope matters
  • Scope and the API surface
  • Tie-in with delivery
  • Try it Yourself

Scoped applications are how you package custom development so it is isolated, portable and safe. Every scoped app has its own namespace (like x_acme_travel), its own tables and files, and explicit rules about what it may touch outside itself. This is the modern default, the opposite of dumping everything in the Global scope.

Why scope matters

  • Isolation, your app can't accidentally break another; cross-scope access is opt-in.
  • Namespacing, tables and script includes are prefixed, avoiding collisions.
  • Distribution, scoped apps publish to the ServiceNow Store or an internal repo.
  • Governance, runtime access to other scopes is controlled by cross-scope access records.
Global is not the safe default. It feels easier to build in Global, but Global code can reach anything and is hard to move and govern. Build in a scope from the start; Global should be reserved for genuinely instance-wide platform tweaks.

Scope and the API surface

// A scoped Script Include exposed to other scopes var TravelAPI = Class.create(); TravelAPI.prototype = { initialize: function() {}, bookedTrips: function(userId) { /* ... */ }, type: 'TravelAPI' }; // Set Accessible-from: All application scopes to share it

Tie-in with delivery

Scoped apps travel between instances via update sets or, better, source control, which is where DevOps and CI/CD pipelines take over.

Want to learn this properly?

Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.

Check your understanding

  1. A scoped app provides...

    • A. Isolation, namespacing and controlled access
    • B. Faster CPUs
    • C. Unlimited storage
    Show answer

    A. Isolation, namespacing and controlled access

    Scopes isolate and namespace custom work.

  2. Cross-scope access is...

    • A. Opt-in and governed
    • B. Always open
    • C. Impossible
    Show answer

    A. Opt-in and governed

    Access to other scopes is controlled by cross-scope access records.

  3. The recommended default for new development is...

    • A. A dedicated scope
    • B. The Global scope
    • C. No scope
    Show answer

    A. A dedicated scope

    Build in a scope; reserve Global for platform-wide tweaks.

Frequently asked questions

What does the term Application scoping refer to in ServiceNow?

Scoped applications are how you package custom development so it is isolated, portable and safe. Every scoped app has its own namespace (like x_acme_travel), its own tables and files, and explicit rules about what it may touch outside itself.

What scripting is involved in Application scoping?

Namespacing, tables and script includes are prefixed, avoiding collisions. Distribution, scoped apps publish to the ServiceNow Store or an internal repo. Governance, runtime access to other scopes is controlled by cross-scope access records.

What is another point to note about Application scoping?

Scoped apps travel between instances via update sets or, better, source control, which is where DevOps and CI/CD pipelines take over.
CallWhatsAppEnquire