• Overview
  • Configuration

Remote

Simplify onboarding for global teams by integrating Remote with directories.

AD & HR syncHCM

Overview

Integrating Remote with Active Directory using ADManager Plus helps organizations streamline user lifecycle management for globally distributed teams. As employees or contractors are added, updated, or offboarded in Remote, the corresponding changes are automatically reflected in Active Directory. This integration bridges HR and IT operations, enabling faster onboarding, consistent access control, and secure offboarding across jurisdictions—without manual coordination.

 

Global onboarding automation

Automatically create AD accounts for new hires or contractors added in Remote, with predefined roles and group access.

 

Real-time access updates

Sync role, department, or contract changes from Remote to Active Directory to keep permissions accurate throughout the employee lifecycle.

 

Secure offboarding

Instantly disable or delete AD accounts when contracts or employment end in Remote, ensuring timely removal of access.

 

How to integrate Remote with ADManager Plus

Prerequisites:

Remote uses OAuth 2.0 to authorize API requests. Please ensure to provide the client_id and client_secret with permissions to retrieve desired information and perform tasks in Remote. Refer to the Remote API references page for more details.

Privileges:

  • To import users (inbound action): Ensure the account used for authorization has permission to read all user accounts.
  • To perform any action or query in Remote (outbound action): Ensure the account used for authorization has permission to perform the desired action.
Note: ADManager Plus comes with a preconfigured set of APIs that help perform basic actions with the integration. If the action you require is not available, please gather the necessary API details from the Remote API documentation to configure under inbound/outbound webhooks to perform the required actions.

Authorization configuration

  • Log in to ADManager Plus and navigate to Directory/Application Settings.
  • Go to Application Integrations, then search and select Remote.
  • Toggle the Enable Remote Integration button on.
  • In the Remote Configuration page, click Authorization.
  • Perform steps to generate client_id and client_secret from Remote, and paste them in the respective value fields.
  • Select Grant Type as Client Credentials.
  • Click Configure.

Inbound webhook configuration

The inbound webhook enables you to get user data from Remote to ADManager Plus and perform desired action available in Automation feature on them. To configure an inbound webhook for Remote:

  • Under Inbound Webhook, click Remote Endpoint Configuration.
  • In the Endpoint Configuration tab, an endpoint, Remote List Employments ENDPOINT, comes preconfigured with an Endpoint URL, API Method, Headers and Parameters fields to fetch user accounts from Remote. However, if you would like to use a new endpoint to import users, you can configure one using the + Add API endpoint button and filling in the required fields per Remote's API references. Click here to learn how. Note:
    • Authorization Header is preconfigured as a header for authenticating API requests as configured during Authorization Configuration.
    • Macros: You can add macros to your endpoint configuration to dynamically change it as per your requirement using the macro chooser component.
    • Refer to Remote's API references and configure additional headers and parameters, if required.
  • Once done, click Test & Save. A response window will display all the requested parameters that can be fetched using the API call. Click Proceed. Note:
    • Refer to Remote's API references to know the Parameters that must be configured to fetch specific parameters.
    • You can configure multiple endpoints for Remote using the + Add API endpoint button. Click here to learn how.
  • Click Data Source - LDAP Attribute Mapping to match endpoints and to map AD LDAP attributes with the respective attributes in Remote.
  • Click + Add New Configuration and perform the following:
    • Enter the Configuration Name and Description and select the Automation Category from the drop-down menu.
    • In the Select Endpoint field, select the desired endpoint and a Primary Key that is unique to a user (e.g. employeeIdentifier). Note: When multiple endpoints are configured, this attribute must hold the same value in all the endpoints.
    • In the Attribute Mapping field, select the attribute from the LDAP Attribute Name drop-down menu and map it with the respective column in Remote.
    • If you would like to create a new custom format for this, click Mapping Attribute.
    • Click Save.
Note: The attribute mapping configured in this section can be selected as the data source during automation configuration to perform the desired action on the list of users received from the API response.

Outbound webhook configuration

An outbound webhook enables you to send changes made in AD using ADManager Plus to Remote and carry out tasks in Remote—all from ADManager Plus.To configure an outbound webhook for Remote:

  • Under Outbound Webhook, click Remote Webhook Configuration.
  • Click + Add Webhook.
  • Enter a name and description for this webhook.
  • Decide on the action that has to be performed and refer to Remote's API references for the API details, such as the URL, headers, parameters, and other requirements.
  • Select the HTTP method that will enable you to perform the desired action on the endpoint from the drop-down menu.
  • Enter the endpoint URL.
  • Configure the Headers, Parameters, and Message Type in the appropriate format based on the API call that you would like to perform.
  • Click Test and Save.
  • A pop-up window will then display a list of AD users and groups on which to test the configured API call. Select the desired user or group on which this API request has to be tested and click OK. This will make a real-time call to the endpoint URL, and the selected objects will be modified according to the configuration.
  • The webhook response and request details will then be displayed. Verify them for the expected API behavior and click Save.
Note: The webhooks configured in this section can be included in Orchestration Templates, which can be used in event-driven and scheduled automations. They can also be applied directly to desired users to perform a sequence of actions on them (under Management > Advanced Management > Orchestration).