scoped-apps

To create a ServiceNow scoped app, open Studio and initialize a new application with a scope name using the x_ prefix convention. Then configure cross-scope access and explicit dependencies for isolated, secure deployment.

ServiceNow scoped apps require specific naming conventions, including x_ prefixes for scope names and structured table naming patterns. These conventions ensure consistent identification and controlled isolation across instances.

Cross-scope access in ServiceNow scoped applications is managed through explicit dependencies and configured permissions. Defining these boundaries allows controlled communication between scopes while maintaining strict application isolation and security.

Yes, you can automate ServiceNow app creation using MCP workflows. The process supports guided scoped app generation, covering application properties, REST API usage, and cross-scope access configuration programmatically.

When publishing scoped apps to the ServiceNow Store, limitations include strict cross-scope access boundaries and basic safety checks. Unsafe scripts are blocked to ensure portable, secure deployments meeting Store requirements.