Mapping Permissions

Learn about how to map permissions in Movebot

Extended Mappings define how user/group permissions should be rewritten and ensure that destination permissions are correctly applied in scenarios where the username/domain is changing. Once permissions migration has been enabled, you will see the option to configure Extended Mappings as an additional step in your project settings.

Example Mappings

Scenario	Source Mapping	Destination Mapping
All usernames mapped to email addresses	*	*@couchdropdemo.com
Domain-only change (username unchanged)	*@couchdrop.io	*@couchdropdemo.com
Username changes and becomes email address	john.doe	[email protected]
Username and domain both change	[email protected]	[email protected]
Group name mapped to group email	Group 1	[email protected]

Importing mappings from a CSV file

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
[email protected],[email protected]
[email protected],[email protected]

Other Options

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.