Google Apps Directory Sync
You must enable API access on your Google Apps domain for GADS to work.
For additional troubleshooting information, please visit the GADS troubleshooting article.
Need to sync data for your school? To sync directory data from your SIS system, you can use Google Apps School Directory Sync.
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.
The latest version of Google Apps Directory Sync is 4.0.3. For more information, see What's New in Google Apps Directory Sync.
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 applicable laws and regulations in using Google Apps Directory Sync, including 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). To the extent that synced data includes personally identifiable information from education records that are subject to FERPA, Google will be considered a "School Official" (as that term is used in FERPA and its implementing regulations) and will comply with FERPA.