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


---

# Set up an instance hierarchy

# Set up an instance hierarchy {#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

Set up an instance hierarchy that best supports your development life
cycle.

## Antes de Iniciar

Role required: none

## Por Que e Quando Desempenhar Esta Tarefa

This example demonstrates how to set up an instance hierarchy where several peer
sub-development instances have the same parent development instance, but a more
complex configuration may be required to handle multiple project teams or other
customer requirements.  
Do not use Team Development with production or test instances.

* Do not use a test or production instance as the parent instance in Team Development.
* Do not make any instance the parent of a production instance.
* Production instances should never have a parent.
When you back out a change on a Team Development instance, it backs out the change all the way back down the chain, including undoing the work on the source instance. This behavior can cause major problems on test and production instances.

## Procedimento

1. Provision a parent development instance on the same software version, such as Dublin, as the target instance, such as production.
2. Clone the production instance to the parent development instance.  
   This step is a recommended best practice.
3. Provision sub-development instances on the same software version as the parent development instance.
4. **Opcional:** Log in to the parent development instance and clone it to the sub-development instances.
5. On each sub-development instance:  
   1. Define [remote instance connections](https://servicenow-prod.fluidtopics.net/IF7N68~2FNOc2PT7lR~Iaw "For each instance, define other instances in the hierarchy as remote instances.") to other instances in the hierarchy that this instance needs to push and pull with.
   2. Select [the parent instance](https://servicenow-prod.fluidtopics.net/s2EDUVaMvimwpzOh9YfRmA "An instance can have multiple peer instances but only one parent instance.").
   3. Pull all changes from the parent instance.
   4. [Grant access rights](https://servicenow-prod.fluidtopics.net/LeASYylQGbyPR~A4g75iJA "To use Team Development, application developers must have a set of credentials for each instance in the Team Development hierarchy.") to appropriate developers.
   {#t_SetUpAnInstanceHierarchy__ol_dkm_w51_bq}