Google Apps Directory Sync

You must enable the Provisioning API on your Google Apps domain for GADS to work. Refer to the Enable API section on page 41 in the Google Apps Directory Sync Administration Guide for instructions.

With Google Apps Directory Sync, you can automatically provision users, groups, and non-employee contacts based on the user data in your LDAP server, such as Microsoft Active Directory or Lotus Domino. Google Apps Directory Sync connects to your Google Apps directory and adds/deletes user accounts to match your existing organizational schema.

The Google Apps Directory Sync configuration wizard guides you through customizing your synchronization and mapping of your LDAP user list to your Google Apps users, nicknames, shared contacts, and groups. You can also synchronize rich user profile data like home/work/mobile phone numbers, addresses, and job titles. To manage your synchronization, you can perform test synchronizations, and configure change limits, notifications, and scheduled synchronizations.

For an in-depth tutorial, watch the Directory Sync: Technical Overview (25 minutes).

Latest Release

The latest version of Google Apps Directory Sync is 3.2.1, released July 2013. For more information, see the Google Apps Directory Sync Release Notes.

Key benefits:

  • Synchronizes your Google Apps user accounts to match the user data in your LDAP server.
  • Supports sophisticated rules for custom mapping of users, groups, non-employee contacts, rich user profiles, aliases, calendar resources, and exceptions.
  • Performs a one-way synchronization. Data on your LDAP server is never updated or altered.
  • Runs as utility in your server environment. No machine outside your perimeter accesses your LDAP directory server data.
  • Includes extensive tests and simulations to ensure correct synchronization.
  • Includes all necessary components in the installation package.

Notice Regarding Google Profiles

Before you enable Google Apps Directory Sync for your organization, please keep a few things in mind:

If Google Profiles is enabled for your organization, the data synced from your institution's directory will be auto-populated into the Google Profile, which your end user may then choose to publish publicly on the web. Your use of Google Apps Directory Sync may in some cases override the user's edits to their own profile fields -- please communicate this to your end users if you have enabled Google Profiles for your organization or if you do so in the future.

Customer acknowledges and agrees that Customer is solely responsible for complying with all laws and regulations that might be applicable to Customer's provision of Google Profiles to Customer's end users, such as the U.S. Family Educational Rights and Privacy Act of 1974 (FERPA), Children's Internet Protection Act (CIPA), and the Children's Online Privacy Protection Act of 1998 (COPPA).


Windows 32-bit | 64-bit
Linux 32-bit | 64-bit



System requirements:

  • LDAP servers: Microsoft Active Directory, Lotus Domino, and most generic Open LDAP servers.
  • Operating systems:
    • Windows XP (SP2), Windows 7, Windows Server 2003/2008/2012
    • Linux
    • Solaris (version 8+, no support for x86)
  • Prerequisites: Read and execute administrative access over to your LDAP server. Experience with LDAP queries and servers.