Destinations are directories or services that OneSync can export users account and data to. Valid destinations include Microsoft Active Directory, Microsoft Azure, and Google GSuite. Each destination requires credentials or authorization in order to access the destination account. The following table details the steps included in an adding a destination to OneSync.
|Destination Details||Yes||Define and edit this destination’s basic details.|
|Select Users||Yes||Select the collection of users that will be exported to this destination.|
|Default Mappings||Yes||Define the mappings between OneSync fields and this Destination’s fields. These mappings will be applied to all users in this destination. For example, you can set the default password for all users in a destination.|
|Custom Mappings||No||For specific sets of users, define the custom mappings between OneSync fields and this Destination’s fields, which will override the default mappings. These users a subset of the previously selected users. Making no custom mappings will mean the sets of users not specified will use the default mappings.|
|Group Mappings||No||Define which destination group a user will be provisioned to given a certain set of conditions.|
|Events & Triggers||No||Define what event will occur when a user triggers a certain set of conditions|
|Save Destination||Yes||You must click the “Save Destination” button in the lower right hand corner in order for changes to take effect|
Destination Mappings, including default, custom, and group mappings, are used to set the values for properties in a destination. To assist in this process, OneSync offers text transformations which can be used to create custom alphanumeric strings based off an individual user’s properties. For example, given the OneSync Fields “%givenName%” and “%surname%”, and the text transformation “LEFT(String, Num of Left Char)”, you can create an string using “LEFT(%givenName%, 3)_ %surname%”, consisting of the left 3 characters of the ng servgivenName, an underscore, and surname.
Note: Selected fields from sources will be formatted with green text in destination mappings, since unmapped fields will return an error.
Custom Mappings define mappings between OneSync fields and a destination’s fields for specific sets of users based on conditionals. Multiple custom mappings are organized by priority, with the greatest priority determined by the lowest priority number.
Note: Making no custom mappings will mean the sets of users not specified will use the default mappings.
Group Mappings select users based on one or more conditionals to add to a destination group. Depending on the destination, you must enter a group path in a specific format:
- Active Directory: “CN=[insert group name here,OU=[insert OU name here]”, without the quotes or brackets. An OU is not required, if the group will be inserted into the base path. If multiple OU’s are used, they should be listed from most specific to least specific.
- GSuite: “ExampleGroupMapping@domain.com”, without the quotes. The group mapping is an email address with a domain registered in GSuite.
- Microsoft Azure: A group name can be entered in plain text with no special formatting.
Note: If users no longer satisfy the conditionals for a group mapping, they will be removed from that group.
Events & Triggers are events that occur when a user triggers a condition based on its properties. The three events include:
- is Disabled: a user is disabled in OneSync by removing it from its origin source
- Field & Value: a user is a assigned a value for the specified property
The two actions include:
- Assign Property and Value: a user is assigned a assigned a value for the specific property
- Move to OU: a user is moved to the specified organizational unit, formatted specifically for the destination type (e.g. “/OU name” for GSuite, “OU=[OU name]” for Active Directory, OU’s do not exist in Azure)
In order to trigger an export, the destination must be mapped with a collection of users from one or more sources. Users will be exported to destinations automatically once exports are both enabled in settings and next to the desired destination on the Destinations page. You can also trigger an export manually by toggling the enable/disable switch next to the desired destination on the destinations page.
Note: OneSync acts a master database for your user accounts. However, it cannot detect changes in a destination. For example, if you add a user directly to a destination, OneSync will not add that user to its own database.
Note: When adding GSuite and Microsoft Azure accounts as destinations, you must have pop-ups unblocked in order to allow a pop-up that will prompt you for account credentials and authorize a connection.
REDIRECT: user collections & conditionals, text transformations, mapping template, mapping terms dictionary