---
title: User management
description: The ServiceNow Provisioner links users from the data store to ServiceNow. The behavior of each provisioning capability is described below.
component: servicenow
page_id: servicenow::pf_servicenow_connector_user_management
canonical_url: https://docs.pingidentity.com/integrations/servicenow/pf_servicenow_connector_user_management.html
revdate: July 8, 2024
section_ids:
  synchronizing-existing-users: Synchronizing existing users
  user-provisioning: User provisioning
  user-updates: User updates
  user-deprovisioning-disabling: User deprovisioning (disabling)
---

# User management

The ServiceNow Provisioner links users from the data store to ServiceNow. The behavior of each provisioning capability is described below.

## Synchronizing existing users

By default, the ServiceNow Provisioner synchronizes users from the data store to the target service by matching an attribute in the data store to the `Username` attribute in the target service.

For example:

* In ServiceNow, Janet's `Username` is `jsmith`.

* In your data store, Janet's `sAMAccountName` is `jsmith`.

* On the **Attribute Mapping** tab, you map the `Username` attribute to `sAMAccountName`.

* When the provisioning connector runs, the data store user is provisioned with a `Username` of `jsmith`. That matches Janet's existing `Username` in ServiceNow, so her information in the data store is synchronized to her ServiceNow account.

You can map the matching data store attribute when you configure your channel in [Creating a provisioning connection](setup/pf_servicenow_connector_creating_a_provisioning_connection.html).

## User provisioning

Triggered by any of the following:

* A user is added to the data store group or filter that is targeted by the provisioning connector.

* A user with "disabled" status is added to the data store group or filter that is targeted by the provisioning connector, and the **Provision disabled users** provisioning option is enabled.

The target is determined by the **Source Location** tab in the provisioning connector configuration.

## User updates

Triggered when a change occurs to a user attribute that is mapped in the provisioning connector configuration.

## User deprovisioning (disabling)

Triggered by any of the following:

* A user is deleted from the user store.

* A user is disabled in the user store.

* A user is removed from the data store group or filter that is targeted by the provisioning connector.