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

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu 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: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

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/zvVDvhpUqXs6sWIyeJUlJw "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}

You can define various combinations of privilege settings for restricted caller access and specify whether access is allowed or restricted for each relationship. This process ensures that your application has the privileges to access the correct scope and not one you don't want to access. 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/dxamKxcyTU~7~BE9MkEk4g "Application scoping protects applications by identifying and restricting access to application files and data.").

Source
:   A specific application resource 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 following combinations:

* Scope-to-scope
* Scope-to-target
* Source-to-scope
* Source-to-target
{#restricted-caller-access-privilege__ul_zcx_jxc_qfb}  
Note:  
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/FK8CI2eDSzXtUZTvgCZhTg "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.").

## 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/r0lv2Mj2OSrO7ZkrKFyBkw "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/r0lv2Mj2OSrO7ZkrKFyBkw)**   
  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/bNyBybTjkTaLXcxCG1lyIQ)**   
  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/FK8CI2eDSzXtUZTvgCZhTg)**   
  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.