---
sourceDocument: Australia Impact
sourceDocumentLink: https://www.servicenow.com/docs/r/impact

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Define My SN Instance environments

# Define My SN Instance environments {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure instance integration settings to define the different environments for your ServiceNow instances and to take advantage of exception processing, definition syncing, and user story tracking in Impact.

Role required: Scan Engine admin and Impact admin.

## System properties {#add-view-scan-engine-related-lists__section_wr2_nx4_ghc}

These are the properties specifically created by the Scan Engine application during installation.

## My SN Instances {#add-view-scan-engine-related-lists__section_djg_qx4_ghc}

Each record indicates an instance connected to the current instance through API integrations.

1. To add an instance to the list, select New.
2. Configure the following fields and settings. {#add-view-scan-engine-related-lists__table_aj5_vx4_ghc__entry__2}

   | Field/Setting | Description |
   |-|-|
   | Instance Name | The name of the instance. |
   | Instance URL | The URL of the instance. |
   | Environment | The instance environment: * Development * Production * Test {#add-view-scan-engine-related-lists__ul_bj5_vx4_ghc} Important: Only one instance can be listed as Production. Otherwise, the integration will fail. |
   | Validated | * Indicates whether the instance has been successfully validated using the UI Action provided in the configuration interface. * You can use the Validate Connection action available on the instance configuration form to attempt a live connection to the target instance using the defined credentials and connection parameters. If successful, the instance is flagged as Validated = true. {#add-view-scan-engine-related-lists__ul_ej5_vx4_ghc} |
   | Connection Status | * Represents the current state of connectivity between local and remote instances. * This field is automatically updated based on the results of the validation process. It reflects the outcome of the live connection test and cannot be edited. * The following values are supported: * Approvals not configured in production * Authentication method is not configured * Connection Valid * Connection Invalid * API User is missing role * User not setup on target instance {#add-view-scan-engine-related-lists__ul_jj5_vx4_ghc} These values help diagnose integration issues, and help with corrective actions. {#add-view-scan-engine-related-lists__ul_gj5_vx4_ghc} |
   | Authentication Type | The instance authentication type: * Basic * OAuth {#add-view-scan-engine-related-lists__ul_pj5_vx4_ghc} |
   | API Credential Config | This field references the credential record used for authentication when Basic is selected as the Authentication Type. Note: This value typically points to a Basic Auth credential stored securely in the system. |
   | OAuth Application Registry | * The OAuth application registry used for cross-instance integrations. * This field is only available if OAuth is selected as the Authentication Type. {#add-view-scan-engine-related-lists__ul_tj5_vx4_ghc} |
   | OAuth User Profile | The OAuth user profile used for cross-instance integrations. |
   [ ]

   {#add-view-scan-engine-related-lists__table_aj5_vx4_ghc}

{#add-view-scan-engine-related-lists__ol_iv4_rx4_ghc}  
Note:  
See [Configure Scan Engine integrations](https://www.servicenow.com/docs/FN2Sk~kUixKI9pnoy4BmsA "Scan Engine integrates with other ServiceNow instances and external agile systems to synchronize definitions, manage exception reasons, create user stories, and enforce governance over app deployments.") for details on integration setup.