---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Create an integration user account

# Create an integration user account {#ariaid-title1}

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

Create a dedicated integration user account and assign the required roles so that the Scan Engine can authenticate and communicate between your ServiceNow instances.

## Before you begin

Complete this procedure in every environment where the Scan Engine will run, for example, development, QA, and production.

Role required: admin (to create users and assign roles)

## About this task

The Scan Engine requires a dedicated integration user in each instance. The user's password is reused in several credential fields during integration setup, therefore, choose a value to store in a secure location before you
begin.  
Tip:  
To display the Password field on the user form, set the system property `glide.user.show.password.field` to <kbd class="ph userinput">true</kbd> temporarily. You can revert this setting after setup is complete.

## Procedure

1. Navigate to AllUser AdministrationUsers.
2. Select New.
3. In the User ID field, enter a name for the account (for example, <kbd class="ph userinput">integration.account</kbd>).  
   Fill in the remaining fields as your organization requires. The user ID and password are the only values that directly affect Scan Engine connectivity.
4. Set a password that you can retrieve later.  
   You will enter this same password as the integration client secret and in the integration user profile. Record it in a secure location before proceeding.
5. Select Save.
6. On the user record, scroll down to the Roles related list and select Edit.
7. Search for <kbd class="ph userinput">sn_se</kbd> and add both of the following roles to the user:
   * `sn_se.internal_rest_integration` -- Internal REST Integration
   * `sn_se.scan_engine_admin` -- Scan Engine Admin
8. Select Save.
9. Repeat this procedure in each additional instance, QA, production, etc., using the same user ID and password.  
   Optional: Set the user Type to Machine or enable Internal Integration User. These settings do not affect Scan Engine connectivity but may align with your
   organization's security policies.

## Result

The integration user account exists in all required instances with the `sn_se.internal_rest_integration` and `sn_se.scan_engine_admin` roles assigned. You are ready to set up the integration
authentication.

## What to do next

Proceed to [Register your instance](https://servicenow-prod.fluidtopics.net/CW_9LTbn1YISzXh4d4sYSg "Register each participating ServiceNow instance in the My SN Instances table before configuring any instance-to-instance integration.")

*[\>]: and then