OneSync is a user provisioning tool that can manage user accounts and their data through various actions including the abilities to create, update, merge, or delete accounts. You can import users from a source, manage the users with OneSync, and export the users to a destination.
Sources are pre-existing directories or files containing user accounts, that OneSync can import data from. Valid sources include Microsoft Active Directory, CSV (comma-separated values) files, ClassLink RosterServer, and ODBC (Open Database Connection). Destinations are directories or services that OneSync can export user accounts and data to. Valid destinations include Microsoft Active Directory, Google GSuite, and Microsoft Azure.
When handling large amounts of users and their data, OneSync offers various functions to manage user accounts including mappings, conditionals, and correlations. Mappings allow you to link user properties, which may be identified differently across each platform, between sources, OneSync, and destinations. Conditionals allow you to select specific collections of users based on defined conditions. Correlations allow you to match and merge duplicate user accounts that would otherwise be considered separate due to differing information between platforms.
OneSync offers three types of syncs: imports from sources, exports to destinations, and dry runs. Dry runs are optional trial runs to test for errors. If a dry run’s activity returns successful, you can export that collection of users with confidence. To gain further insight into these syncs, including their timestamps and statuses, you can view their activity logs, which detail successes and errors per user, and filter them by date.
Once you setup OneSync, you can automate syncs to manage your accounts for you. OneSync acts as middleware to reduce the time and effort needed to maintain account information in an orderly and secure manner.
Note: OneSync exports user account information to a destination through a one way sync, but a destination cannot update users or data in OneSync. This means that once users are exported to a destination, any changes or updates to a user or their account information within the destination will not be sent back or updated in OneSync. Thus, subsequent syncs from OneSync to a destination can overwrite these manual updates and so, any updates to users should be made in OneSync, then exported to a destination.