--- sourceDocument: Australia Enable AI sourceDocumentLink: https://www.servicenow.com/docs/r/australia/intelligent-experiences Release : - australia ft:locale : - en-US ft:publication_title : - Australia Enable AI ft:clusterId : - platai bundleId : - platai workflow : - Platform --- # Multi-Instance Setup # Multi-Instance Setup {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Multi-Instance Setup The Multi-Instance Setup in ServiceNow enables a production (prod) instance to manage multiple sub-production (sub-prod) instances, facilitating centralized or distributed governance and communication, especially for AI Control Tower environments. This hierarchical framework supports efficient management, synchronization, and communication between instances. Show full answer Show less ## Instance Roles and Hierarchy * **Prod Instance:** Can manage both other prod instances and sub-prod instances, making it ideal for centralized governance across an organization. * **Sub-Prod Instance:** Can manage other sub-prod instances but not prod instances; typically used for teams, environments, or business units. ## Configuration Options You can configure the Multi-Instance Framework depending on your organizational needs: * **Centralized Configuration:** One prod instance acts as the manager for all other instances (both prod and sub-prod). This configuration supports a streamlined review process and centralized governance where one instance controls asset states, rules, and policies across all connected instances. * **Distributed Configuration:** Multiple prod instances manage distinct groups of sub-prod instances independently. This setup suits organizations with separate business units or teams requiring autonomous asset governance within a shared environment. ## Post-Configuration Steps * Enable AI Asset data transfer on the prod instance via the AI Control Tower user interface; this automatically configures remaining settings, requiring no additional setup. * Ensure both prod and sub-prod instances run the same AI Control Tower core version (minimum 6.2.4 starting May 2026) to maintain framework functionality. ## Asset Synchronization and AI Inventory * The framework synchronizes assets from sub-prod to prod instances, accelerating review processes, and synchronizes rules from prod to sub-prod instances. * AI inventory synchronization includes AI systems, models, prompts, datasets, and---starting September 2025---AI agents across instances. * Asset states remain environment-specific: assets in sub-prod are marked as under development until activated in prod, reflecting lifecycle progression rather than single-environment status. ## Data and Preferences Management * Enable data sharing preferences to apply production settings across sub-prod instances; this is off by default. * Enable data overflow processing and bursting preferences similarly, with default off settings. * When Multi-Instance is enabled, sub-prod instance preferences for data sharing and processing become read-only, ensuring consistent governance. ## Additional Considerations For comprehensive data security and trust configuration management across instances, refer to the relevant documentation on data sharing and cross-instance trust settings to ensure compliance and secure multi-instance operations. The Multi-Instance Setup enables a prod (manager) instance to manage multiple sub-prod (managed) instances and facilitate communication for AI Control Tower. ## Instance Management Hierarchy overview {#multi-instance-management__section_djs_d2d_yjc} The Multi-Instance Framework uses a hierarchical structure to organize how instances manage and communicate with each other. This hierarchy helps you configure the appropriate manager instance for your environment. ## Instance Roles and Capabilities {#multi-instance-management__section_tkt_32d_yjc} Prod Instance A prod instance can manage both other prod instances and sub-prod instances. This makes it suitable for centralized governance across your organization. Sub-Prod Instance A sub-prod instance can manage other sub-prod instances but can't manage prod instances. sub-prod instances are typically used for specific teams, environments, or business units. ## Configure Multi-Instance Framework with Multiple Prod and Sub-Prod Instances {#multi-instance-management__section_zt3_cfd_yjc} Scenario: You have two prod instances and 6--8 sub-prod instances, and you want to configure the Multi-Instance Framework to manage and synchronize assets across all instances. The Multi-Instance Framework enables a prod instance to manage multiple sub-prod instances and facilitate communication for centralized asset governance. Depending on your organizational needs, you can configure Multi-Instance Framework in two ways * Centralized Configuration- Use when your organization prefers centralized governance and a streamlined review process. * Distributed Configuration- Use when your organization has distinct business units or teams that require independent asset governance within a shared environment. {#multi-instance-management__ul_e1x_vgd_yjc} ## Centralized Configuration {#multi-instance-management__section_vq1_ygd_yjc} Use this configuration if you want a single access move to review and manage data from all instances. 1. Designate one prod instance as the manager instance. 2. Configure all other instances (the second prod instance and all sub-prod instances) to send synchronization requests to the manager instance. {#multi-instance-management__ol_wbn_4hd_yjc} The prod instance controls asset states, rules, and policies for all connected instances. ## Distributed Configuration {#multi-instance-management__section_nwl_23d_yjc} Use this configuration if you want to organize instances into separate management groups. 1. Designate the first prod instance to manage a group of sub-prod instances (for example, 2--3 sub-prod instances). 2. Designate the second prod instance to manage another group of sub-prod instances (for example, 4--5 sub-prod instances). 3. Configure each sub-prod instance to send synchronization requests to its assigned prod instance. ## After configuration {#multi-instance-management__section_p22_lkd_yjc} After configuring the Multi-Instance Framework, enable AI Asset data transfer on the prod instance from the AI Control Tower user interface. When you configure AI Asset data transfer, the remaining values are automatically configured. No additional setup is required. Note: For information about configuring Multi-instance management for AI Control Tower, see [Configure Multi-Instance management for AI Control Tower](https://www.servicenow.com/docs/CYfNU2tJ0Ncvtyt8sSvgWg "Configuring Multi-Instance management for AI Control Tower."). ## AI asset Synchronization {#multi-instance-management__section_c2r_hht_rfc} The Multi-Instance Framework synchronizes assets from sub-prod instances to the manager instance, enabling faster review processes. The framework also synchronizes rules from the prod instance to all sub-prod instances. Note: Starting with the May 2026 release, confirm that both the prod and sub-prod instances are running the same AI Control Tower core version (6.2.4), which is the minimum supported version. Upgrade the prod instance to version 6.2.4 when you upgrade a sub-prod instance to confirm the Multi-Instance Framework functions correctly. AI inventory information : You can include the sub-prod instances to synchronize with the prod instance. This synchronization enables AI inventory information to flow between the instances. When configured, the scheduled job synchronizes AI systems, AI models, prompts, and datasets across instances. Staring with the September (2025) release, the job also synchronizes AI agents. : Note: State of the assets while configuring Multi-Instance management. The production AI inventory displays the actual state of your assets like models, datasets, and skills from a production perspective. However, assets that are active in a sub-prod instance environment remain classified as under development from the sub-prod instance perspective because they are still in testing and not yet live. Due to this distinction, asset states remain separate across environments and don't synchronize. An asset's state transitions to deployed only when the asset and its related records are activated in the production system. In summary, the state indicates the asset's complete lifecycle progression, not its status within any single environment. Data sharing preference : Enable the data sharing preference to apply the production settings to all sub-prod instances. By default, this preference is turned off. Data overflow processing and bursting preference : Enable data overflow processing and bursting preferences to apply the production settings to all sub-prod instances. By default, these preferences are turned off. Note: All the preferences mentioned earlier for a sub-prod instance are available in read-only mode, when Multi-Instance is configured and enabled. For information on Data, see [Data sharing, processing, and security in AI Control Tower](https://www.servicenow.com/docs/m1eaSveCOUa1tK1Cfj987w "Explore the Data sharing, processing, and Security & privacy sections.") For more information on trust concepts and trust configuration management, see [Cross-instance application trust configuration](https://www.servicenow.com/docs/r/platform-administration/grant-access-v2.html).