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


---

# Configure your controller instance

# Configure your controller instance {#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 must identify one of the instances in your app development pipeline as the controller instance. All communication between the instances in your pipeline, including the deployment order for applications in the
pipeline, takes place in the controller instance.

## Antes de Iniciar

Role required: admin

## Por Que e Quando Desempenhar Esta Tarefa

Typically, your production instance should be identified as the controller instance.
All request and approval records are stored on your controller instance.

## Procedimento

1. Navigate to AllApp EnginePipelines and DeploymentsEnvironments.
2. When you are [configuring your
   pipeline environments](https://servicenow-prod.fluidtopics.net/O2n_EgyX47hYCPl9AqEJuw "Set up your app development production and non-production environments (for example, development, test, and/or staging) by adding the URLs and credentials used to access each instance."), decide which instance you want to use as the controller, and select the Is Controller? check box for that instance.  
3. Select Save.  
   When the workflow for the pipeline runs, the non-production instances communicate with the controller instance to determine to which instance the app should next be deployed.