Cross-scope application access decides whether a script in one ServiceNow application can read, write, create or delete resources owned by another application. Three settings shape that decision: the calling application’s design settings, the target table’s access fields, and restricted caller access records held by the target. Check them in that order.
Why cross-scope access is a separate layer
Application access settings decide whether one application can reach resources in another. They resemble access control lists in that they restrict something, but the target differs. Access controls restrict tables and records from users. Cross-scope settings restrict application resources from other applications, so a passing user check says nothing about whether a script from a different scope may run.
Custom applications get a private scope with its own namespace by default. Their tables and business logic stay out of other applications’ reach unless someone grants that access explicitly. The application scope concept page covers the vocabulary first.
Where each setting lives
| Setting type | Who configures it | What it decides |
|---|---|---|
| Application design and runtime settings | Application designers | Whether the application’s scripts may reach cross-scope resources |
| Table design and runtime settings | Application developers | Whether other scopes can see the table and which operations they may run |
| Restricted caller access privilege settings | Admin users and application administrators | Whether a cross-scope script may reach an application, resource or event the target owns |
Application design and runtime fields
JavaScript Mode sets the JavaScript standard the application supports: ECMAScript 2021 (ES12), ES5 Standards Mode, or Compatibility Mode for earlier editions. Runtime Access Tracking controls how script access requests to other applications are recorded. Restrict Table Choices controls what developers see during design. When it is cleared, the application can see tables from other scopes. When it is selected, design choices are limited to the same application.
Administrators grant developers access to other applications’ tables through application design access records. Each record holds a Source Scope (the application asking), a Target Package (the application whose tables become available) and the Application the record belongs to. Once a developer creates configuration records against another application, that application appears as a dependency.
Table design and runtime fields
Can read is the base permission for script objects in other scopes. Can write, Can create and Can delete are offered when Can read is selected. The Allow access to this table via web services check governs inbound web service queries at design time and at run time, and the querying user still needs permission on the table.
Runtime access tracking and privilege records
Runtime access tracking builds a list of script operations and targets that the system authorises to run. It has three options.
| Option | During development | At run time |
|---|---|---|
| None | Nothing is tracked or authorised | Scripts reach other applications as far as table-level settings allow |
| Tracking | A cross-scope privilege record is created per request, status Allowed | The tracked operation runs if table-level settings allow it |
| Enforcing | A record is created per request, status Requested | The operation is blocked until an administrator sets it to Allowed and table-level settings allow it |
In both Tracking and Enforcing, the system stops tracking new requests after installation. During development, the designer must run the application’s script logic so that the requests are recorded and authorised. A branch that does not run during development produces no record to review.
Reading a cross-scope privilege record
Each record in the Cross scope privileges table holds a Source Scope, a Target Scope, a Target Name, a Target Type (table, script include or script object), an Operation and a Status of requested, allowed or denied. Tables support read, write, create and delete. Script includes and script objects support the execute API operation.
| Source Scope | Target Scope | Target Name | Operation | Status |
|---|---|---|---|---|
| My App | Global | incident | Read | Allowed |
| My App | Global | ScopedGlideRecord | Execute API | Allowed |
Administrators can create these records ahead of development to describe the access developers will need. A privilege cannot exceed what the target table object allows. The table object record (sys_db_object) sets that ceiling through fields such as Can delete scopes, so a delete privilege on incident cannot be granted if the incident table object does not permit deletion from other scopes.
Setting runtime access on a table
Table access is set in the application’s own records, and the steps need the admin role.
- Navigate to All > System Applications > Applications.
- Choose Developed for applications created on the instance, or Downloaded for applications downloaded to it.
- Open the application, then select the table in the Tables related list.
- In the Application Access section, set the runtime permissions and select Update.
New application tables allow read access from all application scopes by default. Create, update and delete are disabled, and web services are enabled. Change it before release if the default is wrong for the table.
To deny other scopes entirely, clear all the Can check boxes and the web services check box in the table’s Application Access section. This blocks script API and web service calls from other scopes. To grant them, set Accessible from to All application scopes and enable the four operations and web services. That is the broadest grant these settings offer, so reserve it for tables other applications genuinely need to change.
Restricted caller access on the target side
Restricted caller access lets the target owner control who calls its resources. The target sets Caller Access on a protected resource to either Caller Restriction or Caller Tracking. Caller Restriction denies the call until a reviewer approves it and creates a record with status Requested. Caller Tracking approves the call automatically and records it as Allowed.
A reviewer opens Application Restricted Caller Access under All > System Applications and sets each Requested record to Allowed or Denied. Once a calling source is allowed, its later calls go through. If the calling resource changes, such as an edited business rule script, the record moves to Invalidated and needs a new decision. If application administration is enabled on the target, its own application administrators set access.
Four ways to scope a grant
| Combination | What it covers | Relationship |
|---|---|---|
| Scope-to-scope | All resources in a source scope to all resources in a target scope | Many to many |
| Scope-to-target | All resources in a source scope to one target resource | Many to one |
| Source-to-scope | One source resource to all resources in a target scope | One to many |
| Source-to-target | One source resource to one target resource | One to one |
Records live in the sys_restricted_caller_access table. Status takes Requested, Denied, Allowed or Invalidated. An RCA privilege record must exist in the target application, so the target scope must match the application scope. Selecting an event as the target lets a source queue an event the target registers, but if the event registry’s caller access is None, cross-scope event calls are denied.
Activation has three routes: the Scoped Application Restricted Caller Access plugin (com.glide.scope.access.restricted_caller); requesting the HR Service Delivery or Security Incident Response application, where restricted caller access is active by default; or the Restricted Caller Access system property for Workflow Studio.
Requested RCA records for packaged applications
A real RCA has a source scope equal to the target scope. A requested RCA has a different source scope and waits for the target owner’s approval, so a store application can ask for access without waiting for a platform release. A developer generates requests with the Generate RCA Privileges in Current App related link, and requested records stay synchronised with the real ones.
On installation, scheduled jobs create Requested RCA records in the target for each request packaged in the source. The jobs start after Upgrade Summary has run, so some lag can occur, and the target administrator sees a pending review message. Source developers should agree the request with the target owner before packaging, because that owner decides on install.
Practical checks before release
These checks prevent gaps that otherwise surface after installation.
- Run the full script logic in development, because tracking records what runs.
- Review Requested records in Application Restricted Caller Access before packaging, since the target owner reviews packaged requests on install.
- Check for Invalidated records after editing any calling script.
- Confirm the table object allows each operation before adding a privilege.
For the scope decisions made before any of this work, read the scope boundary guide for app engine builds. For applying these settings on a live instance, see the scoped application architecture work and the instance security and access control guides.
Frequently asked questions
Why can other applications read a new table but not change it?
New application tables default to read access from all application scopes, with create, update and delete disabled.
What happens when runtime access tracking is set to Enforcing?
Each runtime request is recorded as Requested, and the operation stays blocked until an administrator sets the record to Allowed and the table-level settings also permit it. The system stops tracking new requests after installation, so review happens during development.
Why does a restricted caller access record show Invalidated?
The calling resource changed, for example an edited business rule script. An admin user or application administrator must set the record to Allowed or Denied again.
Can a store application request access before it is installed?
It can package the request. The target creates matching Requested RCA records when the source is installed, through a scheduled job that starts after Upgrade Summary has run. The target administrator then approves or denies them.