--- 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 # Multi-instance {#ariaid-title1} Release version: Australia Updated July 27, 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 Framework The Multi-instance Framework in ServiceNow enables a production (prod) manager instance to oversee multiple sub-production (sub-prod) instances, streamlining communication and governance across your organization's AI Control Tower environments. This hierarchical structure supports centralized or distributed management models, facilitating effective asset synchronization and governance. Show full answer Show less ## Instance Roles and Hierarchy * **Prod Instance:** Acts as a manager capable of overseeing other prod and sub-prod instances, suitable for centralized governance. * **Sub-Prod Instance:** Can manage other sub-prod instances but not prod instances; typically assigned to teams, environments, or business units. ## Configuration Scenarios The framework supports two main configurations, depending on organizational needs: * **Centralized Configuration:** One prod instance manages all other prod and sub-prod instances, centralizing asset control and review processes. * **Distributed Configuration:** Multiple prod instances manage separate groups of sub-prod instances, enabling independent governance within a shared environment. ## Post-Configuration Steps After setup, enable AI Asset data transfer on the prod (manager) instance via the AI Control Tower interface. This automatically configures necessary values, requiring no additional setup. Note that configuring Multi-instance requires requesting a Manager instance from the Multi-instance page. ## AI Asset Synchronization and Version Requirements * The framework synchronizes assets from sub-prod instances to the manager instance, accelerating review processes. * Rules are synchronized from the prod instance to all sub-prod instances. * Ensure both prod and sub-prod instances run the same AI Control Tower core version (minimum 6.2.4 as of May 2026) to maintain compatibility. ## AI Inventory Synchronization Scheduled synchronization includes AI systems, models, prompts, datasets, and AI agents (added in September 2025). Asset lifecycle states remain environment-specific---assets under development in sub-prod are marked accordingly until deployed in prod. ## Preferences and Data Management * **Data Sharing Preference:** When enabled, production settings apply to all sub-prod instances (default is off). * **Data Overflow Processing:** Also applies production settings to sub-prod instances when enabled (default is off). * These preferences are read-only on sub-prod instances once Multi-instance Framework is enabled. ## Additional Notes For trust and security management across instances, refer to the cross-instance application trust configuration documentation. The Multi-instance Framework enables a prod (manager) instance to manage multiple sub-prod (managed) instances and facilitate communication for AI Control Tower. ## Instance Management Hierarchy Overview {#configure-multi-instance__instance_manage} 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 {#configure-multi-instance__id_upj_1gz_1kc} 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 {#configure-multi-instance__id_y1s_bgz_1kc} 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 the 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. {#configure-multi-instance__ul_e1x_vgd_yjc} ## Centralized Configuration {#configure-multi-instance__id_yt3_2gz_1kc} Use this configuration if you want a single access move to review and manage data from all instances. 1. Select one prod instance as the manager instance from the list of instances. 2. Configure all other instances (the second prod instance and all sub-prod instances) to send synchronization requests to the manager instance. {#configure-multi-instance__ol_wbn_4hd_yjc} The prod instance controls asset states, rules, and policies for all connected instances. ## Distributed Configuration {#configure-multi-instance__id_zpk_fgz_1kc} Use this configuration if you want to organize instances into separate management groups. 1. Select the first prod instance to manage a group of sub-prod instances (for example, 2--3 sub-prod instances). 2. Select 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. {#configure-multi-instance__ol_nrk_fgz_1kc} ## After Configuration {#configure-multi-instance__id_frk_ggz_1kc} 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: To configure Multi-instance, you must request a Manager instance. For more information on requesting a manager instance, see [Request a Manager instance](https://www.servicenow.com/docs/RZCVtAQ8AYLNrjYL69TBkA "Request a Manager instance from the Multi-instance page to configure multi-instance management."). ## AI Asset Synchronization {#configure-multi-instance__id_fqr_jgz_1kc} 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. Starting with the September 2025 release, the job also synchronizes AI agents. : Note: State of the assets while configuring Multi-instance. The production AI inventory displays the actual state of your assets like models, datasets, and skills from a production perspective. Assets that are active in a sub-prod instance environment remain classified as under development from the sub-prod instance perspective. This classification occurs 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 : Enable data overflow processing to apply the production settings to all sub-prod instances. By default, this preference is turned off. Note: All the preferences mentioned earlier for a sub-prod instance are available in read-only mode, when the Multi-instance Framework is configured and enabled. 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). * **[Request a Manager instance](https://www.servicenow.com/docs/RZCVtAQ8AYLNrjYL69TBkA)** Request a Manager instance from the Multi-instance page to configure multi-instance management.