On This Page

Overview

Permission Preservation determines how permissions are transferred between platforms. You specify how you want the source permissions for folders and files to transfer to the destination platform during the job run.

Preserve Item Authorship/Ownership

The preserve item authorship/ownership feature allows for files being copied/synced/or migrated to maintain their original author/owner information.  In order to preserve authorship, both the source platform connector and the destination platform connector must support this feature. Refer to the Platform Comparison to verify compatibility between your platforms.

While DryvIQ will automatically attempt to map users based on various rules, such as name and actual ID, it is also possible to map specific users from one platform to another. This is useful when a user no longer exists or when a user's name, email, or other identifiable information is different between platforms. 

DryvIQ tracks associations between items and user mappings, similar to permission tracking. Users who created or modified the item or its versions (when applicable) will be displayed on the User mapping tab of the job page. For author/owner preservation tracking to work, the job audit level must be set to at least "Info" (the default level for the DryvIQ user-interface).

Preserve Item Permissions

The item permissions policy determines how you want permissions to be applied with your job execution(s). There are four options available:

• Disable Preserve Item Permissions: If you do not turn on the Preserve Item Permissions toggle, the item permissions will not be preserved. No permissions will be passed from source to destination. This is the default. You must turn on this toggle in order to use any of the other preserve item permissions options.

• Add permissions: The current permissions existing on impending transfers (on files or folders) will be preserved as they are transferred on both the source and the destination. This is the recommended setting.

• Prefer permissions on the source: This will reconcile permissions with the source, which will remove permissions from the destination if they do not match the source. This will keep things in sync if the destination folder levels more permissions than the source. This is a good option for sync jobs that are constantly moving back and forth to keep everything as intended.

• Assign permissions from file: Permissions for items on the source will not be retained. Instead, new permissions will be assigned based on information provided in a csv formatted file stored on the source platform. See Permissions Import for information about how to structure your permission import file.

Permission Failures

Permission failure policy determines what should happen with your job execution(s) should it encounter failures. You can select to transfer the item even if there is an issue with applying permissions to the item. This is the recommended setting. If preferred, you can choose to