Should the user sync provision new users apart from updating existing users?
When syncing users, how do we uniquely identify users? Is it by email address, username or an external identity?
Should the user sync deactivate users? If yes, what is the logic?
Please provide a field mapping that indicates how the data from the source system will map to Jive data:
Profile Field (visible)
Extended Property (not visible)
password (for non-federated users)
manager (for org chart only)
Will the sync process provide for permission group assignments?
If the answer to Question 3 is "Yes", please describe the rules for doing so.
Are there other special rules that the sync process needs to be able to handle, such as custom formatting of fields, merging field values together, a single value that needs to be populated in multiple Jive profile fields?
Are there any special rules with respect to enabling or disabling users?
How are blank field values to be handled?
Is there any chance that users may have duplicate usernames or email addresses?
Is there a need to merge multiple users from the source file into a single Jive user?
Are you able to produce, on a regular basis, a UTF-8 encoded CSV file containing the user data described above, and transfer the file via SFTP to Jive?