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


---

# Create an exclusion policy

# Create an exclusion policy {#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

Application developers can create an exclusion policy to prevent pushes or pulls to
particular instances in the team development hierarchy.

## Antes de Iniciar

Role required: none

## Procedimento

1. Navigate to AllTeam DevelopmentExclusion Policy.
2. Click New.
3. Complete the Exclusion Policy form (see table).
4. Click Submit.  
   {#t_CreateAnExclusionPolicy__table_s5f_fmb_bq__entry__2}

   | Field | Description |
   |-|-|
   | Name | Enter a unique description of the policy. |
   | Policy | Select when the policy applies. Options include: * Push only * Push and Pull * Pull only {#t_CreateAnExclusionPolicy__ul_cj5_hmb_bq} |
   | Remote Instance | \[Optional\] Select a specific remote instance to ignore changes from during pull operations. Leaving this field blank ignores changes from all remote instances. |
   | Table | Select which table to ignore changes for. |
   | Conditions | Select any additional criteria a change must meet to be ignored other than the table name. This field is only visible when the Policy is Push only. |
   [Tabela 1. Exclusion policy form]

   {#t_CreateAnExclusionPolicy__table_s5f_fmb_bq}