---
sourceDocument: Brazil Impact
sourceDocumentLink: https://www.servicenow.com/docs/r/impact

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Integrations across multiple instances

# Integrations across multiple instances {#ariaid-title1}

Release version: Brazil  
Updated October 28, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
A stack with more than two instances needs an OAuth provider registry and an OAuth client registry for every instance in the stack.

A development and production pair is the simplest integration stack. Most organizations run more non-production instances, such as development, QA, and test. In that case, every instance in the stack needs an OAuth provider registry and an OAuth client registry for each instance, and you export those records to every instance.

## Stack model

{#multi-instance-integration__entry__2}

| Instance role | Records required |
|-|-|
| Production | A My SN Instances record for itself, marked Production, and one for each non-production instance it communicates with. |
| Each non-production instance | A My SN Instances record for itself, marked Development or Test, and one for production. |
| Every instance in the stack | An integration user, and an OAuth provider registry and an OAuth client registry for each instance in the stack. Export both records to every instance. In a stack of development, test, and production, each instance has six OAuth registry records, one provider and one client for each instance. |
[Table 1. Records by instance role]

Important:  
Only one instance in the stack can be designated Production.

## Setup order

Complete the setup for the first development and production pair before you add more instances. Then repeat the non-production steps for each additional instance.

1. Create the integration user on each instance, using [Create an integration user account](https://www.servicenow.com/docs/L7u6ANwPaPvCvoYiwpoeyg "Create a dedicated integration user account and assign the required roles so that the Scan Engine can authenticate and communicate between your ServiceNow instances.").
2. Register every instance in the stack, using [Register your instance](https://www.servicenow.com/docs/qVtcMVX4ueNM5WLtwJLobg "Register each participating ServiceNow instance in the My SN Instances table before configuring any instance-to-instance integration.").
3. Set up OAuth for the first development and production pair, using [Configure the OAuth authentication method development instance](https://www.servicenow.com/docs/JMYCW35QMol3B5RjYlAheQ "Set up OAuth authentication for instance-to-instance Scan Engine integrations using several stages, an integration user account, an OAuth2 configuration record, and provider and client application registries.") and [Configure the OAuth authentication method production instance](https://www.servicenow.com/docs/9E6CdgkChtoyz8~j8M11mg "Export OAuth records from the development instance, import them into the production instance, and correct Key Management Framework (KMF) credential encryption. Configure development-to-production authentication so that both instances can validate their connections to each other.").
4. For each additional non-production instance, create an OAuth provider registry and an OAuth client registry on that instance. Export both records, and import them into every other instance in the stack. Then create the My SN Instances record for that instance on production.
5. Grant KMF access on each instance that receives imported records, using [Grant Key Management Framework access on an instance](https://www.servicenow.com/docs/XWpnleOsoKncEGm_C4OnwA "Give the setup user KMF roles and approve the Scan Engine decryption policy so that imported credentials can be decrypted on the instance.").
6. Validate every My SN Instances record on every instance, using [Validate your instance connection](https://www.servicenow.com/docs/D7DhNjyDy2a0UaVjDi5Uqg "Validate the connection between registered instances to confirm that authentication and My SN Instances configuration are correct before enabling integrations.").