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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Application access settings

# Application access settings {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Application access settings determine whether one application can access resources from
another application.

Application access settings are similar to access controls (ACLs) in that they allow you to
restrict access to certain resources, but instead of restricting tables and records from users
they restrict applications resources from other applications. There are several ways to set
cross-scope access.  
{#c_ApplicationAccessSettings__table_cxq_1b5_n1b__entry__4}

| Setting type | Use | Description | Access setting location |
|-|-|-|-|
| [Application design and runtime settings](https://www.servicenow.com/docs/dXmokANa8wpetu2QlO7dBg "The application design and runtime settings determine whether an application can access cross-scope resources.") | Your application or application script requires access to a cross-scope resource. | Application designers can configure the following application access settings for the entire application. * Specify whether cross-scope tables can be selected during design-time activities. * Specify when scripts can run on cross-scope resources. * Specify what JavaScript standard the application supports. {#c_ApplicationAccessSettings__ul_yjf_qlf_cv} | Access determined by the cross-scope privilege record owned by the calling application. |
| [Table design and runtime settings](https://www.servicenow.com/docs/Ixs5e4DqedHQtjNMWfX44w "The Application access fields determine whether a table is accessible to other applications during design-time or run-time operations.") | A cross-scope application or web service requires access to perform CRUD operations on a table. | Application developers can also configure application access settings for individual tables. * Specify whether the table is available to other application scopes. * Specify what runtime operations from other application scopes the table supports. * Specify whether the table can be selected during design-time activities. * Specify whether the table can be accessed from web services. {#c_ApplicationAccessSettings__ul_v5y_1qf_cv} | Access determined by settings on the target table. |
| [Restricted caller access privilege settings](https://www.servicenow.com/docs/tHQ~eSI2k_dzCwREkUG4Ug "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.") | A cross-scope application or script requires access to your application or application resource. | Admin users can configure the following application access settings for an entire application scope or application resource. * Specify whether a cross-scope script can access your application scope or an application resource. * Track cross-scope requests for access to application resources. * Approve or deny cross-scope requests to access application resources. {#c_ApplicationAccessSettings__ul_b5c_tlg_n1b} | Access determined by the restricted caller access record owned by the target application. |
[ ]

{#c_ApplicationAccessSettings__table_cxq_1b5_n1b}