---
sourceDocument: Zurich ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/platform-administration

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Cross-instance application trust configuration

# Cross-instance application trust configuration {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](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 Cross-instance application trust configuration

Cross-instance application trust configuration in ServiceNow's multi-instance management enables secure and streamlined communication between multiple instances for enabled applications.
It centralizes the management of trust settings across your multi-instance environment, ensuring that instances can securely share data and messages through defined trust relationships.
Show full answer Show less  
The core concept is the **trust profile**, which specifies how instances trust each other for a particular application and its capabilities. This profile must be propagated to participating instances to automate trust configuration, simplifying administration and reducing manual setup.

## Key Features

* **Trust Profile:** Defines the trust configuration between instances for a specific application and its granular capabilities, enabling secure cross-instance communication.
* **Centralized Trust Management:** Designate a production instance as the managing instance to maintain and propagate trust profiles to managed instances, automating synchronization and reducing errors.
* **Trustor and Trustee Roles:** Clarifies which instance trusts (trustor) and which is trusted (trustee), enabling controlled data sharing and message exchange at the application capability level.
* **Trust Configuration Tables:** Display trust relationships by application, capability, and trustee instance, allowing administrators to review and create trust records as needed.
* **Management of Instances:** Separate views for managing instances (managers) and managed instances, ensuring clear delegation of trust configuration responsibilities.

## Practical Application for ServiceNow Customers

By leveraging cross-instance trust configuration, customers managing multiple ServiceNow instances can:

* Securely enable applications to communicate across instances with trust profiles that define necessary permissions.
* Use a centralized production instance to manage trust settings and automatically distribute updates to all managed instances, improving efficiency.
* Control trust relationships at a granular level per application and capability, ensuring precise security management.
* Monitor and edit trust settings through trust tables, providing transparency and control over cross-instance interactions.
* Assign and configure managing and managed instances to establish clear trust management hierarchies within the multi-instance environment.

## Next Steps

To implement cross-instance trust configuration:

* Define trust profiles for the applications and capabilities that require cross-instance communication.
* Designate managing instances and configure managed instances to enable automatic trust profile propagation.
* Regularly synchronize trust profiles using management features such as the **Sync Trust Profile** button to keep trust configurations consistent across instances.
* Review and maintain trust tables to ensure trust relationships reflect your organizational security requirements.  
Multi-instance management provides a mechanism to streamline the management of trust configurations across your entire multi-instance environment.

The multi-instance capability introduces new concepts, describing how communication is supported across instances for enabled applications and their capabilities. In order to do this securely, you need to define how these instances
trust each other. This can be defined as a trust profile. The trust profile defines how a set of instances communicate for a given application. In order for this profile to be applied to each instance, that profile needs to be propagated
out to the instances that will participate in a given application.

Multi-instance management offers a centralized mechanism for configuring and maintaining trust settings across your multi-instance deployment. This simplifies the process of propagating trust settings to all instances under your
control by designating a production instance by designating a production instance to manage the trust configurations on all the instances it should manage remotely.

## Trust concepts {#grant-access-v2__section_ets_kdr_qdc}

Trust profile

:   The Trust profile defines the ideal trust configuration of all the instances that participate in a specific application. The trust profile is specific to an enabled application. It defines how the instances leverage the application
    capabilities to communicate with each other. Once the application's trust profile with the trust configuration for each instance is defined, it can be shared with the managed instances. This will trigger the automatic population of
    trust tables within those instances. This automation depends on whether there is a Trust profile manager defined. If not, trust configuration needs to be manually created on each instance.

    For example, if you're currently logged into sub-prod 2 and Prod 1 has management privileges over sub-prod 2, you can use the Sync Trust Profile button on Prod 1 to distribute trust profiles to all instances
    under Prod 1's management. The updated trust profile will then be reflected on Prod 2.

Capabilities and operations

:   Capabilities are application features that would be leveraged for cross instance communication. It is a group of granular operations that are available as a part of the application.Enabled applications within an instance
    possesses a trust profile, which is established for every capability it exposes. To ensure seamless communication between instances for these capabilities, a trust configuration must be defined. This trust profile encompasses all the
    necessary trust configurations between instances for a specific application and its capabilities.

Trustor and Trustee
:   Trustor can be defined as the instance that is trusting the other instances with viewing its data and/or receiving messages from the trusted instance.  
    For example, you're logged into Prod 1. There are 2 other sub prods- sub-prod 1 and sub-prod 2. If Prod 1 trust sub-prod 1 and sub-prod 2, then Prod 1 is the Trustor and sub-prod 1 and sub-prod 2 are Trustees.  
    Note:  
    The trust concept works on the instance for a given application at the capability level. The table that lists the instances trusted by your instance has 3 columns: application, capability, and Trustee instance.

    When instances are required to communicate, they consider the application trust configuration before
    communicating with each other.

    For example, if an enabled application on Prod 1 needs to send a message to Sub-prod 1 and Sub-prod 2, these sub-prods must trust Prod 1 to receive the message and act on it. In this scenario, the
    sub-prods are the trustors, and Prod 1 is the trustee.

    If Prod 1 doesn't trust sub-prod 1 and sub-prod 2, messages from the sub-prods to Prod 1 are not processed.

    You can go to the trust table and create a new trust
    record.

## Trust configuration management {#grant-access-v2__section_blg_rn2_rdc}

Managing instances

:   The table shows the instance that is designated as the manager instance for the instance you are logged into. If you are logged into the managing instance, the table will be blank.For example, you're logged into Prod 1. The
    instances shown in the Managing Instances table are the instances that are being managed by Prod 1 for particular applications.

Managed instances

:   The table shows the instances that you are managing.For example, you're logged into Prod 1. The instances shown in the Managed Instances table are the instances that Prod 1 is managing for the specified
    applications.

    Managed instances must grant permission to managing instances in order to automatically distribute trust profiles.  
    Note:  
    An instance can't be both a managing and a managed instance. An instance can manage several instances simultaneously. An application within an instance can be managed by only one instance at a time.
* **[Configure Manager Instances](https://www.servicenow.com/docs/M5KntfmmJVYfdmpoLXCJOw)**   
  Implement the following steps to configure the Manager Instances in Multi-Instance Management.
* **[Configure Managed Instances](https://www.servicenow.com/docs/9rMjQnUoEZXQUQS~R2INqQ)**   
  Implement the following steps to configure the Managed Instances in Multi-Instance Management.