Basic trust configuration for data sync applications
Summarize
Summary of Basic trust configuration for data sync applications
Certain ServiceNow applications enable data visibility and sharing across multiple instances within a customer’s account. This capability is governed by a trust configuration that is specific to each instance and application. Administrators can manage these settings to control data sharing for both production and non-production instances.
Show less
Key Features
- Trust Configuration Location: Managed via All > Multi-Instance Management > Trust Configuration in the ServiceNow platform.
- Default Settings: Non-production instances allow sharing only with production instances by default; production instances do not share data with any other instances unless explicitly configured.
- Instance Role Changes: Promoting or demoting instances between production and non-production resets all custom data sharing settings to defaults.
- Access Control Columns:
- Grant access: Editable by the logged-in instance to permit or revoke data sharing with another instance.
- Is granting access: Read-only indicator showing whether another instance has granted access to the logged-in instance.
- Granular Control: Trust is managed per application and per instance, allowing precise control over which instances can share data.
Practical Use and Examples
- When logged into a production instance (e.g., Prod1), you can grant or revoke access for another instance (e.g., Prod2) for a specific application such as Subscription Management.
- When logged into a non-production instance (e.g., Sub-prod2), you can similarly manage access permissions for production or other non-production instances.
- The system indicates current access statuses, helping administrators understand existing data sharing relationships and make appropriate adjustments.
Benefits for ServiceNow Customers
This trust configuration framework ensures data security and privacy across your ServiceNow environment while providing flexibility to share data where necessary. By configuring these settings, you can:
- Maintain strict control over data visibility between production and non-production instances.
- Customize sharing policies based on business needs for each application and instance.
- Ensure compliance with organizational and regulatory data governance requirements.
- Easily identify and modify trust relationships through a clear, user-friendly interface.
Certain ServiceNow applications have the ability to provide data visibility across instances within a customer’s account.
Data visibility is protected by a trust configuration per instance, per application. You can configure the data sharing for production and non-production instances for the applicable applications by navigating to .
By default, non-production instances allow application data sharing with production only. Production instances do not allow application data sharing with any other instance. However, these can be updated by the admin for each instance based on business needs.
If you demote a production instance to non-production, or promote a non-production instance to production, all previous customizations to data sharing settings are reset to the default configuration.
The Grant access column indicates the permission granted by the instance that you’re currently logged in to for the instance named in the same row’s instance column. The Is granting access column displays whether or not the instance mentioned in the Instance column has granted access to the instance you’re currently logged in to; it can’t be edited.The following are some examples for data sharing restrictions between instances.
Logged in to Prod1
In the following example, you’re logged in to Prod1. Prod1 has granted access to the instance Prod2 for the application Subscription Management, as indicated by the True value in the Grant access column.
Prod2 hasn’t granted access to Prod1, as indicated by the False value in the Is granting access column.
To revoke access for the Subscription Management app from Prod1 to Prod2, update the value in the Grant access column to False while logged in to Prod1.
Logged in to Prod2
In the following example, you’re logged in to Prod2. Prod1 has granted access to the instance Prod2 for the application Subscription Management, as indicated by the True value in the Is granting access column.
Prod2 hasn’t granted access to Prod1, as indicated by the False value in the Grant access column.
To grant access from Prod2 to Prod1 for the Subscription Management application, update the value in the Grant access column to True while logged in to Prod2.
Logged in to Sub-prod2
In the following example, you’re logged in to Sub-prod2. Prod1 hasn’t granted access to the instance Sub-prod2 for the application Subscription Management, as indicated by the False value in the Is granting access column.
Sub-prod2 has granted access to Prod1, as indicated by the True value in the Grant access column.
To revoke access from Sub-prod2 to Prod1 for the Subscription Management application, update the value in the Grant access column to True while logged in to Sub-prod2.
Logged in to Sub-prod3
In the following example, you’re logged in to Sub-prod3. Sub-prod4 has granted access to the instance Sub-prod3 for the application Subscription Management, as indicated by the True value in the Is granting access column. Sub-prod3 has also granted access to Sub-prod4, as indicated by the True value in the Grant access column.