Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

On This Page

Shared Links Policy

Several platforms support the option to share files and folders through a link. The Shared Links Policy determines whether "domain" or "anyone" links are transferred from the source to the destination. Permission Preservation must be turned on for the job in order to use this policy.

Notification emails may be generated on the destination platform when shared links are transferred.

The following platforms support shared links. Refer to the Platform Comparison to see conflict between platforms.

  • Box (See below for additional information.)

  • Dropbox

  • Microsoft SharePoint Online (Microsoft Office 365/Microsoft OneDrive for Business Online)

  • Google Workspace

Box

Box supports links for the following:

  • (Anyone) People with the link: Anyone with the link view only.

  • (Company) People in your company view only.

  • (Company) Invited people only: shared link will be view only; invited users can be set as view or edit.

  • Box has an additional option to view and download but we do not support transferring that and this is not an applicable option for SPO.

DryvIQ only supports anyone or domain (company). When transferring to Microsoft SharePoint Online, the Box options will be translated as follows: 

  • Anyone: Anyone with the link can view.

  • Company: People in company with the link can view.

  • Company Internal: People in company with the link can view, and the invited users from within the company will be added to the Microsoft SharePoint Online direct access list with the corresponding edit or view rights.

  • Company External Users: People in company with the link can view, and the invited external user will go to the pending access and requests page.

Sharing Terms

Anyone/Anonymous: Links that can be shared with anyone.

  • Box: open

  • Dropbox: public

  • Google: anyone

  • SharePoint: anonymous

Domain: Links that can be shared only within your organization or enterprise.

  • Box: company

  • Dropbox: team_only

  • Google: domain

  • SharePoint: organizational

Shared Links Support

DryvIQ handles shared links differently per platform. The following list defines different ways DryvIQ handles shared links.  Refer to the table below to see how DryvIQ handles shared links for each platform that supports this feature. 

READ/VIEW RIGHTS UNSAFE-ONLY: Links will be transferred as “view only.”

READ/VIEW AND WRITE/EDIT: Both "read" and "edit" links can be transferred.

ANYONE LINKS UNSAFE-ONLY: Anyone/Anonymous are links that can be shared with anyone.

SUPPORTED: Feature is fully supported by the Platform and DryvIQ.

NOT SUPPORTED: Feature is available by the Platform but not supported by DryvIQ.

NOT APPLICABLE: Feature is not supported by the Platform.

 

 

Box

Dropbox

Microsoft SharePoint Online

Google Workspace

Number of Links

1 link per file or folder

1 link per file or folder

multiple links per file or folder

Max 2 links; anonymous and/or a domain

Rights

READ/VIEW RIGHTS UNSAFE-ONLY

READ/VIEW RIGHTS UNSAFE-ONLYVIEW -ONLY

READ/VIEW AND WRITE/EDITDEDIT

READ/VIEW AND WRITE/EDITRITE/

Expiration Date

SUPPORTED

SUPPORTEDPPORTED

ANYONE LINKS UNSAFE-ONLY

READ/VIEW RIGHTS UNSAFE-ONLYFE-ONLY

Link Passwords

NOT SUPPORTED

NOT SUPPORTEDORTED

NOT APPLICABLE

NOT APPLICABLE

Disable Download

NOT SUPPORTED

NOT SUPPORTEDT

NOT APPLICABLE

NOT APPLICABLE

User and Group Mapping Policy

User and group mapping policies allow accounts and groups to be mapped between platforms. Maps can be created before creating the job in the Maps area. If a map that uses the source and destination selected for the job exists, the map field will default to this map when you select the mapping option. If a map doesn’t exist, you need to use the corresponding Create new map policy link to create the map before you can select to use the user or group map policy. Refer to Maps for information about creating new maps.

Create User Map Modal

Create Group Map Modal

You cannot assign a mapping documents to an intelligent migration job when specifying the permission preservation for the job. Instead, mapping policies for intelligent migration jobs are automatically assigned to child jobs based on their source and destination platforms. If there are no matching maps, no mapping will be used. If there are multiple matching maps, the child job will not be created, and an error will be present on the parent job noting that multiple maps are not supported.

  • No labels