---
title: "Set up AD Integration Rules"
slug: "set-up-ad-integration-rules"
tags: ["IT Pro"]
updated: 2026-07-28T14:14:37Z
published: 2026-07-28T14:14:37Z
canonical: "help.lanteria.com/set-up-ad-integration-rules"
---
> ## Documentation Index
> Fetch the complete documentation index at: https://help.lanteria.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Set up AD Integration Rules
AD integration rules are set up in the **AD Integration Rules** field under Settings and Configuration (go to **Settings** > **Settings and Configuration** > **Integrations > AD Integration**). By default, this setting is empty.
.png)
The rules are set in the XML format.
…
## Header Attributes
In the header, define the following attributes:
- login, password – credentials for accessing AD. Leave the login and password empty if you want to use the Timer Service account for accessing AD. Otherwise, specify credentials of an account with the relevant permissions.
- domainNameOrIP – domain name or IP address of the AD server.
- IntegrationBy – parameter used as key during the integration. If left empty or set to ‘login’, the integration is performed by ***login***, i.e. AD account. Other options are: ‘***globalID***’, which means that integration is performed based on the Global Employee ID (a field in the employee card), and ‘***email***’, which means that integration is performed based on the employees’ email addresses stored in the Lanteria HR employee cards.NoteThe values used by the IntegrationBy attribute must be unique.
## AD Rule Attributes
The AD integration rules are defined as follows:
- direction attribute determines where the changes are made. Acceptable values are ‘in’ for changes in AD to be populated to Lanteria HR and ‘out’ for changes in Lanteria HR to go to AD
- ADField attribute is the internal name of an AD field
- ESField attribute is the internal name of a field from the Employees list.
Any field from the Employees list can be integrated. The fields *lastname*, *fullname*, *location*, *email*, *workphone*, *homephone*, *cellphone*, *city*, *zip*, *state*, *address*, *country*, *jobposition*, *jobrole*, *department*, *legalentity*, and *manager* can be listed using only their internal names, for example, ESField='manager'. All the other fields must be listed as ‘Employee:{InternalFieldName}’, for example, ESField='Employee:BusinessCardTitle'.
*Note**Field names listed as ‘Employee:{InternalFieldName}’ are case-sensitive.*
You can add as many rules as required.
## AD Rules Example