Audience: (ClassLink Administrator)
OneSync exports and updates user in a destination via connections called user destination links. These links match users in OneSync to their respective counterpart accounts in a destination. To manage these links, OneSync offers an additional tool called correlation.
The goal of correlation is to link users in OneSync to users who already exist in the target application for any subsequent actions taken in OneSync and to avoid any user duplication on export. The process of correlation involves creating sets of increasingly specific conditions to match OneSync Users to users already present in the target application. Any remaining users can be correlated or matched manually.
Correlation also offers additional tools to manage user destination links. You can break these links between accounts if you want to restart the provisioning process. These links may also become broken, rendering a OneSync user useless until that link is unlinked. In any case, correlation can help you manage these links.
Note: Correlation is a background job. This allows you to initiate correlation, navigate away from the page, and return to it when you need to.
- User Selection
- Unlinked Users
- Linked Users
- Broken Links
- Disable Users
- Finishing Correlation
Before Correlating users, you can select specific Organization Units to stage destination users from. Selecting no specific Organizational Units will stage all users in the Destination. While OneSync stages users for correlation, an animation will play to show you the visual progress of the staging. You can always come back to this tab to Re-Stage Users.
Correlation will stage users into two columns, a OneSync column with OneSync users and a destination column with destination users. User destination links are depicted as blue lines connecting one user from each column to each other. In addition users in both columns are staged with a full list of their mappings and properties. You can any user's mappings by clicking the dropdown arrow to the right of their name to expand their user information cell.
Unlinked Users include OneSync users that have not been exported or matched to corresponding accounts in a destination. Unlinked users also include those users in a destination that have not been linked to an existing OneSync user. The purpose of this tab is to match as many users as possible through automatic rulesets and manual matching to minimize duplicate accounts with subsequent exports.
To start, you can create and run a ruleset. Access rule creation by clicking the "View & Add Rulesets" button in the top right of the page. In this view, you will be guided in the creation of conditions and the review of matches based on those conditions. Create rules to reduce the amount of manual matching you will have to do. Try creating rulesets that will, first, accurately match as many users as possible. Subsequent rulesets can consist of more specific conditions to match users not yet matched by broader conditions. Rulesets output a list of After running a ruleset, click "Re-Match" to revise a ruleset, or "Accept" to apply that ruleset and match the outputted users.
You can also manually match users. Select Users, one from each table, and review their properties by expanding each of their rows. If selected users are a match, press the "Match Selected" button at the bottom left of the view.
Linked users include OneSync users that are connected to their respective user accounts in a destination via user destination links. This tab will include users that were successfully exported from OneSync to a destination.
Here, you can unlink users which will effectively delete their user destination links. You can either unlink users individually by clicking on an individual link between the desired user accounts, or you can unlink all users by pressing the "Unlink All Users" button in the top right hand corner.
Unlinking users will delete the link that allows OneSync to update the complementary user accounts within a destination. Thus, you should only unlink accounts if you want to restart the provisioning process for that account.
Broken links include OneSync users that have user destination links to a destination, but found no corresponding users to match those users. This means that the corresponding user accounts within a destination were somehow deleted. Thus, attempts to update users through these broken links will force an error within OneSync since there are no corresponding users within the destination to update.
Users with broken user destination links cannot be updated until their links have been unlinked. To unlink all broken links, simply click the "Unlink All Broken" button in the top right hand corner.
Note: OneSync users with corresponding destination users in OU's other than those selected during the User Selection process will appear in the Broken Links tab. For proper correlation, make sure that the OneSync users that you would like to analyze are in your selected OU's.
The Disable Users tab displays destination users within your selected organization units. Here, you can manually disable individual or groups of users. You can highlight an individual user to disable it. You can click the "Disable All Users" button in the top right hand corner. Or, you can you can search for and disable more specific groups of users. To do so, use the search bar to enter your query, then click the "Disable Filtered Users" button in the top right hand corner. This fitler is currently only available for names, but will be expanded to more fields.
Correlation is complete when there are no more OneSync users to match to users in the target Destination or when no more accurate matches can be made. Correlated OneSync users will have user destination links connecting them to corresponding destination users so that they can update these accounts in subsequent syncs. Any remaining OneSync users still do not have user destination links, but can be exported as new users to the destination.
When finishing a correlation, you will be prompted to run a Dry Run or Export. It is advised to run an export to update all accounts analyzed during correlation.
Updated: Jan 2019