---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/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


---

# Exclusion policies

# Exclusion policies {#ariaid-title1}

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

You can exclude certain files from change tracking by creating an exclusion
policy.

When a change matches an exclusion policy, the change does not generate records in the local
changes list. The change still generates local version records and Update Set records as normal.
See [Creating an
Exclusion Policy](https://servicenow-prod.fluidtopics.net/nbhmHoccIxhW9L~P1esrOw "Application developers can create an exclusion policy to prevent pushes or pulls to particular instances in the team development hierarchy.").  
Note:  
The exclusion policy applies to changes identified during a reconciliation operation. If you create an exclusion policy after a reconciliation, Team Development still tracks the changes until the next reconciliation.