---
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


---

# Definitions integration

# Definitions integration {#ariaid-title1}

Release version: Brazil  
Updated October 27, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The Definitions integration manually syncs new, customized, and overridden definitions from development to production and the other instances.

When you customize or override a definition on a development instance, use the Sync Definition action to send the change to your production instance so that scans run consistently across environments. Definitions don't sync automatically. You can sync individual definitions
or multiple definitions in bulk.

## Prerequisites

* My SN Instances registration is complete. See [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.").
* Authentication is configured. See [Configure the Basic authentication method](https://www.servicenow.com/docs/sqSEawQaR6_jbGjrlIhFCQ "Confirm an integration user, create a Basic authentication record, then connect your instances using basic authentication. Basic authentication is supported but OAuth is recommended for production environments.") or [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.").
* Role required: `sn_se.scan_engine_admin`.

## Where to configure

Manual definition sync actions appear only on instances whose environment is Development. Set the environment on each development record as described in [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.").

Selecting Enable definition synchronization on a development instance only makes the manual Sync Definition action available. It doesn't sync definitions on its own, and the setting is read-only on production. Definitions also don't sync after you clone an instance. To update definitions after a clone, sync them again from a development instance.

## Sync direction

Definitions sync from development to production first. From production, they sync to every other registered instance in the stack, except the development instance where the definition originated. Only development instances can start a manual definition sync.

Definitions don't sync directly between development instances. When you sync a definition from one development instance, production receives it and sends it to the other registered instances, including other development instances.  
Note:  
Enable definition synchronization on only one development instance. That way, definition changes come from one instance, and your team has one place to work on definitions.

## What syncs

The following definition states can be synchronized:

* New definitions created on the development instance.
* Customized definitions where default behavior has been modified.
* Overridden definitions where the default has been replaced entirely.
* **[Sync definitions](https://www.servicenow.com/docs/4Afqut1S3PtGbunY7HmUBQ)**   
  Enable definition synchronization and push new, customized, or overridden definitions from a development instance to production.