---
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 design access to a table

# Example denying all design 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 other application scopes from creating configuration records on
application data tables.

Typically, this is to prevent any other applications from changing the functionality of a
table. Denying access requires setting the following value in the table record.  
{#c_ExampleDenyingAllDesignAccess__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 |
| Allow configuration | Disabled |
[Tabela 1. Denying all design-time access]

{#c_ExampleDenyingAllDesignAccess__table_o4z_wbc_br}  
Figura 1. Limiting design-time access to this application scope only

The following diagram illustrates the effect of denying other application scopes the ability to
create configuration records.  
Figura 2. Limiting design access to this application scope only