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


---

# Example denying all runtime access to a table

# Example denying all runtime access to a table {#ariaid-title1}

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

You can prevent script API and web service calls from other application
scopes.

Typically, this is to prevent any other application from creating or modifying data in the
table. Denying access requires setting the following value in the table record.  
{#c_ExampleDenyingAllRuntimeAccess__table_o4z_wbc_br__entry__2}

| Field | Value |
|-|-|
| Accessible from | This application scope only |
| Can read | Disabled |
| Can create | Disabled |
| Can update | Disabled |
| Can delete | Disabled |
| Allow access to this table via web services | Disabled |
[Tabela 1. Denying all runtime access]

{#c_ExampleDenyingAllRuntimeAccess__table_o4z_wbc_br}  
Figura 1. Limiting runtime access to this application scope only

The following diagram illustrates the effect of denying other application scopes access to
application tables from script API and web service calls.  
Figura 2. Deny all runtime access permissions to application tables