Archer User Profile and Contact Synchronization

Assigning accountability for tasks, findings, and remediation is a key component for nearly all Archer use cases. Several Archer use cases utilize the Contacts application to store metadata about users. The user profile information, including the credentials used to log into the Archer Platform, is stored separately. Therefore, the Platform stores similar user and contact data in two different locations.

Archer Exchange: With the Archer Exchange, the Archer team has created a broad selection of supplemental, value-added offerings to help you get your unique risk management program on the right path, right from the start. You can leverage the Archer Exchange offerings to expand the use of Archer solutions into new business processes and address specific industry, geographic, regulatory, or technical requirements.


Release history

Release date

Release

Notes

2025.10

December 2025

Overview

The Archer User Profile and Contacts Synchronization Tool & Utility uses the Archer RESTful API and a data feed to synchronize fields, if populated, between the User Profile and the Contacts application.

Archer User Profile and Contacts Synchronization is available to both Archer on-premises and Archer SaaS clients.

Key features and benefits

The Archer User Profile and Contacts Synchronization Tool & Utility establishes a consistent process for synchronizing user and contact data and assures data integrity between this metadata. It automates this process and improves data consistency across these two data sets.

With Archer User Profile and Contacts Synchronization, organizations can:

  • Sync User Profile key attributes with the Contacts application.

  • Enable a one-way sync between these data sources.

  • Reduce the manual effort of creating or updating the contacts records.

Prerequisites

Components

Recommended Software

Archer Solution Area This offering applies to various solution areas.
Archer Use Case Enterprise Catalog
Archer Applications Contacts
Uses Custom Objects No

Requires Archer On-Demand Application (ODA) License

This offering does not require an Archer On-Demand Application (ODA) license.

Archer requirements

Archer Platform Release 2025.10 and later

Supported Archer Environments

  • On-premises

  • Archer SaaS

Components

The following diagram provides a high-level overview of the data flow process for the Archer User Profile and Contacts Synchronization.

Diagram  Description automatically generated

Installing Archer User Profile and Contacts Synchronization

It is assumed that the reader has both working knowledge of all products involved, and the ability to perform the tasks outlined in this section. Administrators must have access to the documentation for all products to install the required components.

Archer use cases that utilize the Contacts application must be installed and working prior to the integration.

To configure the Archer Platform, you must first download the following components from Archer Exchange.

File Name

Description

User Profile Contact Sync (JST).dfx5

Archer JavaScript Transporter Data Feed

signed-UserProfileContactSync.js

Signed JavaScript file used by the JavaScript Transporter data feeds.

Setting up data feeds

Configure the data feeds

Important: Before you upload a JavaScript file, configure JavaScript Transporter settings in the Archer Control Panel. For more information, see Configure the JavaScript Transporter Settings.After setting up the data feeds, you can schedule them to run as needed per your organization’s requirements. For more information on Scheduling data feeds, see the Scheduling Data Feeds section.

Troubleshooting

  • Do not include default.aspx in the Archer URL.

  • Note that the Archer instance name is case sensitive.

  • Assure that dedicated, active Archer user account credentials are used in the data feed.

  • All Source Fields automatically populate when you import the data feed.  To repopulate the source fields again, upload the SampleOutput.xml file.

  • The following list of fields are supported in ODATA Filter.

    • AccountStatus

    • Company

    • DistinguishedName

    • DomainId*

    • FirstName

    • Id*

    • LastName

    • MiddleName

    • Title

    • UserName

    *Indicates that when using Domain Id or Id field within the ODATA filter, do not enclose its value with Single Quote(‘). However, all other field values should be enclosed with single quote(‘).

Certification environment

Date Tested: December 2025

Product Name

Version Information

Operating System

Archer

2025.10

Virtual Appliance