---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Set the application scope, application resource, and event access

# Set the application scope, application resource, and event access {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

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.

## Antes de Iniciar

If you enable application administration for the target application, only application
administrators of the target application can set access to an application. If
application administration is not enabled, an admin user can set access to an
application.  
Role required: application admin or admin  
Nota:  
To learn about application-specific administrator roles and delegated development, see [Access control rules in application administration apps](https://servicenow-prod.fluidtopics.net/S35DvENwYrqSfCD9N1yEvg "By default, when application administration is enabled for a scoped application, ACL rules for the scoped application are applied. If no ACL rules for the scoped application are found, global ACL rules can apply.") and [Delegated development and deployment](https://servicenow-prod.fluidtopics.net/Utp_DuonEy0vWlmieLjUMw "Delegated development allows designated users without a system admin role to develop or deploy applications on the ServiceNow AI Platform.").

## Por Que e Quando Desempenhar Esta Tarefa

You can set the following restricted caller access privilege settings combinations:

* Scope-to-Scope
* Scope-to-Target
* Source-to-Scope
* Source-to-Target
{#scope-resource-access__ul_zcx_jxc_qfb}  
Nota:  
In the Rome release, we have enforced that an RCA privilege record must be present in the target application to grant access to a resource. This means that the target scope must match the application scope.

## Procedimento

1. Navigate to AllSystem ApplicationsApplication Restricted Caller Access.
2. On the form, fill in the fields.  
   {#scope-resource-access__table_sjf_q2q_zdb__entry__2}

   | Field | Description |
   |-|-|
   | Operation | Operation performed on the target resource. * Read * Write * Create * Delete * Execute API {#scope-resource-access__ul_tjf_q2q_zdb} |
   | Source | Cross-scope record that is accessing a restricted application resource. |
   | Source Scope | Scope of the calling application. |
   | Source Table | Table that contains the Source record. |
   | Source Type | Type of record that is calling the application resource: * ACL * Business Rule * Document Title * Flow * Flow Action * GlideScopedEvaluator * Inbound Email Script * Orchestration RunScript Activity * Record Producer Script * Service Portal Widget * Scheduled Script * Scope * Script Include * UI Action * UI Macro * UI Page * Workflow Activity {#scope-resource-access__ul_ujf_q2q_zdb} For example, to allow access from an entire application, select Scope. |
   | Status | Status of the access request: * Requested * Denied * Allowed * Invalidated {#scope-resource-access__ul_vjf_q2q_zdb} Nota: If a calling resource changes, the restricted caller access record status changes to Invalidated. If you enable application administration, only application administrators of the target application can update the status of a request. |
   | Target | Record of the requested resource. |
   | Target Scope | Scope of the requested resource. |
   | Target Table | Table that contains the Target record. |
   | Target Type | Type of requested resource. * Event Nota: An event is a special type of target for restricted caller access. By selecting an event in a target scope, you give a source application permission to queue an event that is registered as part of a target application. However, if you set the caller access on the event registry to None, it prevents cross-scope access calls to an event. This setting combination is a one-to-one relationship. To learn more about events, and their function, see [Events](https://www.servicenow.com/docs/access?context=events&version=australia&pubname=australia-platform-administration&ft:locale=en-US). If you set caller access to None on the event registry, the cross-scope access calls to an event are denied. * Scope * Table * Script Include {#scope-resource-access__ul_wjf_q2q_zdb} For example, to allow access to an entire application, select Scope. |
   [Tabela 1. Restricted Caller Access fields]

   {#scope-resource-access__table_sjf_q2q_zdb}
{#scope-resource-access__steps_qjf_q2q_zdb}
* **[Scope-to-scope settings](https://servicenow-prod.fluidtopics.net/oXlwW7j~6E5EwZ1xzTdSsA)**   
  Allow or deny access of all application resources in a source scope to all application resources in a target scope. This setting combination is a many-to-many relationship.
* **[Scope-to-target settings](https://servicenow-prod.fluidtopics.net/1F11p8kDqh7gUGg0Hyk~eg)**   
  Allow or deny access of all application resources in a source scope to a specific application resource (business rule, table, script include, or event) in a target scope.
* **[Source-to-scope settings](https://servicenow-prod.fluidtopics.net/oV4RBOkqOSgPKVVA7B__AQ)**   
  Allow or deny access of a specific application resource in a source scope to all application resources in a target scope.
* **[Source-to-target settings](https://servicenow-prod.fluidtopics.net/4kxmHSAcJ6YwSRaxgzkgiA)**   
  Allow or deny access of a specific application resource in a source scope to a specific application resource in a target scope.