Restricted caller access privilege settings

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 [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.

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.

For more information, see Requested restricted caller access (RCA).

Restricted caller access privilege setting combinations

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.

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

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.

Activating application restricted caller access

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 Flow Designer.

For more information, see: Activate application restricted caller access.

• Activate application restricted caller access
  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
  Track cross-scope requests for access to an application resource and approve or deny requests.
• Set the application scope, application resource, and event access
  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.