---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Restricted caller access privilege settings

# Restricted caller access privilege settings {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Restricted Caller Access Privilege Settings

Restricted caller access privilege settings allow ServiceNow customers to manage cross-scope access to applications and their resources, such as roles, business rules, and events.
This feature enables the tracking, approval, or denial of access requests, enhancing security and control over inter-application interactions.
Show full answer Show less  

## Key Features

* **Tracking Access Requests:** Records are created to track cross-scope access requests when caller access is restricted or when cross-scope scripts attempt to access resources.
* **Privilege Combinations:** Define various settings for access control, including scope-to-scope and source-to-target relationships, allowing for specific resource permissions.
* **Activation Methods:** Activate restricted caller access via the Scoped Application Restricted Caller Access plugin or by utilizing specific applications like HR Service Delivery.

## Key Outcomes

By using restricted caller access privilege settings, customers can ensure that only authorized applications and users can access specific resources, thereby maintaining data integrity and security. This capability allows for better management of application interactions and streamlined request handling, ultimately leading to a more secure ServiceNow environment.  
Define cross-scope access to an application, application resource (such as an access
control role, a business rule, a UI action, or a script include), or event. You can even use
these settings to allow or deny requests for access.

## Restricted caller access privilege settings overview {#restricted-caller-access-privilege__section_mrt_shj_gqb}

Restricted caller access \[sys_restricted_caller_access\] records track cross-scope applications or scripts that request access to an application, application resource, or event in the ServiceNow AI Platform. The ServiceNow AI Platform creates sys_restricted_caller_access records when one of these actions occurs:  
* Caller access is set to Caller Restriction or Caller Tracking.
* A cross-scope script attempts to access an application resource or event.  
  Note:  
  A system scope to target scope is an example of a cross-scope.
{#restricted-caller-access-privilege__kdein_jeifin}

You can use these records to do these tasks:

* Track cross-scope requests for access to an application resource. You can use access requests to determine which applications need access to resources and data from other application scopes.
* Approve or deny any cross-scope requests for access to application resources or events. For example, you can create a Restricted Caller Access record to allow access for all scope-to-scope requests.

{#restricted-caller-access-privilege__ul_pym_f3y_f2b}

For more information, see [Requested restricted caller access (RCA)](https://www.servicenow.com/docs/1JBaZnmq4iL~jpJ3jKA0rw "You can use a requested RCA to grant store apps access to protected resources in the ServiceNow AI Platform without the need to wait for the next family release. If you have the system admin or application admin role, you can review requested RCAs and approve and deny them.").

## Restricted caller access privilege setting combinations {#restricted-caller-access-privilege__section_ubv_s5v_g2b}

As a target application owner, you can define various combinations of privilege settings for restricted caller access and specify whether access is allowed or denied for each relationship. RCA records must be created in the target
application scope to control access to your application's resources. You can define various combinations of privilege settings for restricted caller access and specify whether access is allowed or restricted for each
relationship.  
You can define various combinations of the following settings:

Scope
:   All application resources in a selected source or target scope. To learn more about application scopes, see [Application scope](https://www.servicenow.com/docs/70Zkk9ge6vOzIXzLJVO1Yg "Application scoping protects applications by identifying and restricting access to application files and data.").

Source
:   A specific application resource (such as a business rule, script include, or table) in a selected source scope.

Target
: A specific application resource in a selected target scope.  
These restricted caller access privilege settings combinations include, but are not limited to, the following combinations:

* Scope-to-scope: Control access from all resources in a source application to all resources in your target application
* Scope-to-target: Control access from all resources in a source application to a specific resource in your target application
* Source-to-scope: Control access from a specific source application resource to all resources in your target application
* Source-to-target: Control access from a specific source application resource to a specific resource in your target application
{#restricted-caller-access-privilege__ul_zcx_jxc_qfb}

For more information about these access setting combinations and to learn how to create each combination, see [Set the application scope, application resource, and event access](https://www.servicenow.com/docs/aQj7tCO1bevxWxFzmaUR0A "Create a record in the Restricted Caller Access Privileges [sys_restricted_caller_access] table to set cross-scope resource access requests. Approve or deny requests from a source scope or source scope application resources to a target scope or to target scope application resources.").  
Note:  
Source application developers who need to request access to resources in another application should coordinate with the target application owner. You can package Requested RCA records in your application, which will then be
reviewed and approved or denied by the target application administrator upon installation.

## Activating application restricted caller access {#restricted-caller-access-privilege__section_crw_swq_4bb}

You can activate application restricted caller access through one of the following
methods:  
* Activate the Scoped Application Restricted Caller Access plugin (com.glide.scope.access.restricted_caller).
* Request the HR Service Delivery or Security Incident Response applications. By default, restricted caller access is active in these applications.
* Enable the Restricted Caller Access system property for Workflow Studio.
{#restricted-caller-access-privilege__ul_prl_vwq_4bb}

For more information, see: [Activate application restricted caller access](https://www.servicenow.com/docs/LNiwToizAprRsfDqmRmiRg "You can activate the Scoped Application Restricted Caller Access plugin (com.glide.scope.access.restricted_caller) if you have the admin role.").
* **[Activate application restricted caller access](https://www.servicenow.com/docs/LNiwToizAprRsfDqmRmiRg)**   
  You can activate the Scoped Application Restricted Caller Access plugin (com.glide.scope.access.restricted_caller) if you have the admin role.
* **[Define cross-scope access to an application resource](https://www.servicenow.com/docs/wuZ1NLJnsdb3pZYuTovswg)**   
  Track cross-scope requests for access to an application resource and approve or deny requests.
* **[Set the application scope, application resource, and event access](https://www.servicenow.com/docs/aQj7tCO1bevxWxFzmaUR0A)**   
  Create a record in the Restricted Caller Access Privileges \[sys_restricted_caller_access\] table to set cross-scope resource access requests. Approve or deny requests from a source scope or source scope application resources to a target scope or to target scope application resources.