Account and Group Maps
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.
Create a Map
You can create maps through Connections or when creating a job. Once a map is created, a map can be applied to any job during the job on the Permission preservation page. Use the information in this section to assist you with creating a user map in the user interface. You can also create maps using REST API calls.
Creating a Map through Connections
Select Connections from the left menu.
Select User maps or Group Maps.
Select Create user map or Create group map.
The corresponding Create map modal opens. (See images below for reference.)
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. Use the table below to assist you.
Select Done to create the map.
Create Account Map Modal
Create Group Map Modal
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.
Field | Map | Description | Required |
|---|---|---|---|
Link matching user IDs | Account | Match accounts by ID. | Optional |
Link matching user names | Account | Match accounts by name. | Optional |
Link matching group names | Group | Match accounts by name. | Optional |
Link matching user email addresses | Account | Match accounts by email. | Optional |
Link matching user usernames | Account | Match accounts by username. | Optional |
Link matching group display names or captions | Group | Match accounts by display name or captions. |
|
Use fuzzy matching | Account | Fuzzy matching performs partial matching on all fields selected on supported platforms. | Optional |
Retain external users | Account | 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 | Account | 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 | Account | 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 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 |
Creating a Map During Job Creation
Select Jobs.
Select Create job.
Select the options you want to use for your job.
On the Advanced page, select Permission preservation.
When you advance to the Permission preservation page, Preserve item authorship/ownership and/or Preserve item permissions must be selected.
The User and group mapping policy section displays.
Select Create new user map policy or Create new group map policy depending on the map you want to create.
The corresponding Create map modal opens. (See modal images above for reference.)
Enter a name for the map you are creating. A name is required to save the map.
Select the source and destination connections the map uses.
Select the options you want to use for the map. (Use the table above to assist you.)
Select Done to create the map.
Managing Maps
If you created a map that you no longer need, you can remove the map.
Select Connections and select either User maps or Group maps depending on the map type.
Find the map and click the ellipses (...) on the right side of the map tile.
Select Delete.
Select Yes to confirm you want to delete the map.
Action Currently Unavailable
If you receive an "Action currently unavailable" message when attempting to delete a map, the application is unable to delete it. The most common reason is that the map is attached to a convention job (User Job Mapping job or Home Drive Mapping job) and cannot be deleted. In order to delete the map, you need to either remove the account map from the job’s configuration page or delete the job. If you choose to delete the job, it may take up to 30 minutes (or longer in some instances) for DryvIQ to delete the job form the database. Once the job is deleted from the database, you will be able to delete the map. Note that an account map can be referenced by more than one job, so you need to remove all job references before you can delete the map.
Notes on expected behavior
If the user is NOT in the account map but the shared item to this missing user is NOT 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 shared to the root folder, there will only be one entry on the overview. Each item will still have an log entry warning