---
title: "Rocket Chat LDAP Data Sync Settings Guide"
slug: "ldap-data-sync-settings"
description: "Learn how to set LDAP data sync in Rocket Chat. Ensure secure communications, identity accuracy, and compliance across your workspace."
updated: 2026-10-26T16:48:00Z
published: 2026-10-26T16:48:00Z
canonical: "docs.rocket.chat/ldap-data-sync-settings"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocket.chat/llms.txt
> Use this file to discover all available pages before exploring further.

# LDAP Data Sync Settings

![](https://cdn.us.document360.io/6ae79a05-7252-45d0-96e8-8f375e07b1b2/Images/Documentation/Premium(1).svg)

> [!WARNING]
> From Rocket.Chat 9.0.0, LDAP is available on Starter workspaces and on all premium plans (Commercial, Government, and Defense). It is not available on Community workspaces. See [Our Plans](/v1/docs/our-plans) for details.

Once you have configured LDAP User Search, the next step is setting up **Data Sync** to keep your Rocket.Chat users aligned with your LDAP directory. These settings control how user data is imported, updated, and mapped.

## Data Sync Options

This setting controls how LDAP users are identified, merged, updated, and assigned default values during synchronization with Rocket.Chat.

| Field | Description |
| --- | --- |
| **Unique Identifier Field** | The attribute(s) that link an LDAP user with a Rocket.Chat user. You can provide multiple values, separated by commas, to ensure the correct match. Default: - `objectGUID` - `ibm-entryUUID` - `GUID` - `dominoUNID` - `nsuniqueId` - `uidNumber` - `uid` |
| **Merge Existing Users** | If enabled, when an imported LDAP user matches an existing Rocket.Chat user (same username), their data will merge and update instead of creating a duplicate account. |
| **Update User Data on Login** | Automatically updates user data from LDAP every time the user logs in. |
| **Update User Data on Login with OAuth services** | Allows user data updates when logging in via OAuth. |
| **Default Domain** | Defines a domain that is appended to usernames when an LDAP record does not provide an email. This ensures every user gets a unique email in Rocket.Chat. **Examples:** - `username@rocket.chat` - `unique_id@rocket.chat` |

## Avatar

This setting defines how user profile pictures are synchronized from LDAP.

| Field | Description |
| --- | --- |
| **Sync User Avatar** | Syncs profile pictures from LDAP. |
| **User Avatar Field** | The LDAP field used as the avatar source. Leave empty to use `thumbnailPhoto` by default, falling back to `jpegPhoto`. |

## Mapping

This setting specifies how LDAP attributes are mapped to Rocket.Chat user fields.

| Field | Description |
| --- | --- |
| **Username Field** | Defines the username for new users. By default, this is `sAMAccountName`. You can also use template tags. **Example:** ```bash #{givenName}.#{sn} ``` |
| **Email Field** | The LDAP attribute used for user email addresses. |
| **Name Field** | The LDAP attribute used for the user's display name. |
| **Extension Field (optional)** | The LDAP attribute used to assign user extensions for the [Rocket.Chat Voice via SIP integration](/v1/docs/configure-voice-via-sip-integration). |

With these settings configured, Rocket.Chat keeps your user data consistent with LDAP while avoiding duplication issues and ensuring smooth authentication.