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


---

# Define a remote instance

# Define a remote instance {#ariaid-title1}

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

For each instance, define other instances in the hierarchy as remote
instances.

## About this task

For example, to set up remote instances for Sub-Dev 1:

## Procedure

1. If IP address access control is enabled, log in to the remote instance and add Sub-Dev 1 as an exception. {#t_DefineARemoteInstance__step-1-add-exception}
{#t_DefineARemoteInstance__step-1-add-exception}
2. On Sub-Dev 1, navigate to Team DevelopmentRemote Instances.
3. Click New.
4. Define the remote instance, such as Dev-Parent, by completing the form (see table).  
5. Click Submit. {#t_DefineARemoteInstance__step-5-submit}
{#t_DefineARemoteInstance__step-5-submit}
6. Repeat [step 1](https://servicenow-prod.fluidtopics.net/ILI2nKrR68L8crxazg0M3Q#t_DefineARemoteInstance__step-1-add-exception) through [step 5](https://servicenow-prod.fluidtopics.net/ILI2nKrR68L8crxazg0M3Q#t_DefineARemoteInstance__step-5-submit) for each instance in the hierarchy that this instance needs to push and pull with (for example, Sub-Dev 2 and Sub-Dev 3).  
   {#t_DefineARemoteInstance__table_mbs_gx1_bq__entry__2}

   | Field | Description |
   |-|-|
   | Name | Enter a unique name describing the instance. |
   | Type | Specify whether the remote instance is a development, test, or UAT instance. |
   | Active | Specify whether the local instance communicates with the remote instance as a member of Team Development. Team Development operations such as comparing changes between instances or selecting a parent instance are only available for active remote instances. |
   | URL | Specify the URL of the remote instance using the appropriate transfer protocol. Each remote instance record should have a unique URL. Creating duplicate records with the same URL can cause errors. |
   | Username | Enter the user on the remote instance who authorizes Team Development operations on the instance. This user account must have an appropriate role on the remote instance. |
   | Password | Enter the password of the authorizing user. |
   | Short description | \[Optional\] Enter any other relevant information about the remote instance. |
   [Table 1. Remote instance form]

   {#t_DefineARemoteInstance__table_mbs_gx1_bq}

*[\>]: and then