On This Page
Overview
A user account or group map provides the ability to explicitly associate users and groups for the purposes of setting authorship and permissions on items transferred. These mappings can happen automatically using rules or explicitly using an exception. Accounts or groups can be excluded by specifying an exclusion, and unmapped users can be defaulted to a known user. Here are a few things to consider when creating an account or group map:
A source and destination connection are required and need to match the source and destination of the job that will be referencing the user or group map.
A map can be created before or during the creation of the job.
A map can be used across multiple jobs.
Once updated, the updates will not be reapplied to content that has already been transferred.
Creating a Map
Click Migrate in the navigation menu on the left.
Click Maps.
The page defaults to User maps. Use the menu to select Group maps if you want to create or manage a group map.
Click the create map button.
The corresponding Create map modal opens.
Enter a name for the map you are creating. A name is required in order to save the map.
Select the source and destination connections the map uses.
Select the options you want to use for the map. See below for information about each mapping option.
Select Done to create the map.
Mapping Policy
DryvIQ will attempt to map users or group from one platforms to another using the rules you select in this section. Note that all options are flagged as optional; however, you must select at least one of the following options in order for the map to work: id, name, username, email, display name, or retain external users.
User Map Mapping Policy
Field | Description | Required |
|---|---|---|
Link matching user IDs | Match accounts by ID. | Optional |
Link matching user names | Match accounts by name. | Optional |
Link matching user email addresses | Match accounts by email. | Optional |
Link matching user usernames | Match accounts by username. | Optional |
Use fuzzy matching | Fuzzy matching performs partial matching on all fields selected on supported platforms. | Optional |
Retain external users | Retain guest account permissions and authorship. This option is not available for all connectors. This option will not be applied to User Account Mapping jobs. | Optional |
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. | Optional |
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) | Optional |
Group Map Mapping Policy
Option | Description | Required |
|---|---|---|
Link matching user IDs | Match accounts by ID. | Optional |
Link matching group names | Match accounts by name. | Optional |
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. | Optional |
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. |
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 individually, and each item has 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. Each item will still have a log entry warning.
Creating a Map During Job Creation
If you want to use a group or user map but do not create the map before you create the job that will use the map, you must create the map when creating the job. You must enable Permission Preservation for the job and turn the Preserve item authorship/ownership and/or the Preserve item permissions toggle on. This displays the User and group mapping policy section at the bottom of the page. Click Create new user map policy or Create new group map policy depending on the map you want to create.
