Learn about how to map permissions in Movebot
Mapping permissions allow you to configure translations between source and destination users and groups. This is used when migrating between two domains or from On-Prem to the cloud.
Example mapping syntax
user1@couchdrop.io
user1@couchdropdemo.com
Group 1
group1@couchdropdemo.com
Administrator
administrator@couchdropdemo.com
*
*@couchdropdemo.com
For situations where the username format is changing, you can add explicit mappings for each user. When migrating a large organization, you can create a CSV file of mappings that can be imported.
An example CSV file is:
source,destination
michael@couchdrop.io, michael.lawson@couchdropdemo.com
chris@couchdrop.io, chris.roy@couchdropdemo.com
Tweak the permission migration further
Send Notification Invitations
Send email notifications to users when permissions are added.
This option is not supported by all cloud platforms.
Exclude Unmapped Permissions
Only include permissions for users that are included in the mappings.
This option is useful for preventing re-sharing with external users.
Exception Rules
Prevent permissions from being migrated under certain circumstances.
Learn about how Movebot scans permissions.
As part of a scan, permissions will be scanned from the source. You can then use the scan results to inspect the permissions on the source. Make sure check Enable File/Folder Permission Preservation during setup to use this feature.
To check the permissions on an individual file or folder, go to Discovery Scan within your project, highlight your target item, and click *Details, then Sharing.
Additionally to the reporting available in the front end, you can download two reports on file permissions:
Permissions Report
A CSV export of all permissions detected on the source by file and folder.
Applied Permissions Report
A CSV export of applied permissions
Learn how to manually map permissions.
Permissions can be manually configured from a CSV file, or the Box collaborators report. When enabled, Movebot will not query for permissions in the source system, rather it will look for permissions in the provided CSV file.
If you are not using the Box collaborators report, the format of the permissions CSV file is as shown in the example below.
filename,collaborator permission,collaborator login
/Case Studies,Editor,jack@couchdrop.io
/FolderX/Case Studies,Editor,jack@couchdrop.io
From your Box admin console, go to Reports > Create Report and click Select Filters on the row for the collaboration report.
If you want to migrate your entire organisation, you can leave the filters blank, or you can generate the report for specific users you wish to migrate.