Creating Automatic User and Group Mappings
Learn how to create a map that automatically matches accounts or groups from the source to the destination.
Written by Andrea Harvey
Updated at May 13th, 2025
Table of Contents
Overview
The first step in creating a user or group map is to specify the automatic mapping rules you want to use. DryvIQ will attempt to map users or groups from one platform to another using the rules you select when creating the map. Note that all options are flagged as optional; however, you must select at least one of the following options for the map to work. Learn more about the options below.
User Map Mapping Policy
| Option | Description |
|---|---|
| Link matching user IDs | Match accounts by ID. |
| Link matching user names | Match accounts by name. |
| Link matching user email addresses | Match accounts by email. |
| Link matching user usernames | Match accounts by username. |
| Use fuzzy matching | Fuzzy matching performs partial matching on all fields selected on supported platforms. |
| Retain external users |
Retain guest account permissions and authorship.
This option is not available for all connectors. See External Account Permissions for more information.
This option will not be applied to User Account Mapping jobs. |
| Attempt to resolve first | This option is only available when Retain external users is selected. This option retains guest account permissions and authorship but attempts to resolve the account against a destination account first before retaining the permissions and authorship utilizing an external user account. |
| Do not attempt to resolve first |
This option is only available when Retain external users is selected. This option retains guest account permissions and authorship utilizing an external account without first attempting to resolve the account against a destination account.
Note: External email addresses already associated as a guest account in OneDrive for Business/Office 365 will work regardless of whether this option is selected.
This is most commonly used for Network File Share (NFS)
|
Notes on Expected Behavior
- If the user is NOT in the account map but the shared item to this missing user is NOT in the root, each item will be logged on the Overview report for the job individually, and each item will have a log history showing permission failure.
- If users are NOT in the account map but are shared to the root folder, there will only be one entry on the Overview report for the job. Each item will still have a log entry warning.
Group Map Mapping Policy
| Option | Description |
|---|---|
| Link matching user IDs | Match accounts by ID. |
| Link matching group names | Match accounts by name. |
| Link matching group display names or captions | Match accounts by display name or captions. |
| Use fuzzy matching | Fuzzy matching performs partial matching on all fields selected on supported platforms. |
Unmapped Policy
Both user and group maps allow you to select how you want DryvIQ to handle users or groups that can’t be matched to a user or group on the destination. Select the option you want to use.
| Option | Description |
|---|---|
| Match unmapped users/groups to a default user/group | Any unmapped users or groups will be assigned to a default user or group. When you select this option, a list of users or groups (based on the type of map you are creating) on the destination displays. Select the user or group you want to use. |
| Skip unmapped users/groups | Unmapped users or groups will be skipped. |
| Log a warning in the audit log and skip unmapped users/groups | Unmapped users or groups will be skipped, and a warning will be added to the job audit log. |