> For the complete documentation index, see [llms.txt](https://docs.movebot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.movebot.io/using-movebot/permissions-and-metadata/mapping-permissions.md).

# Mapping Permissions

Permission 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 Permission Mappings as an additional step in your project settings.

&#x20;&#x20;

*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`              | `jdoe@couchdropdemo.com`   |
| Username and domain both change            | `john.doe@couchdrop.io` | `jdoe@couchdropdemo.com`   |
| Group name mapped to group email           | `Group 1`               | `group1@couchdropdemo.com` |

&#x20;

### **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.

&#x20;

*An example CSV file is:*

```
source,destination
michael@couchdrop.io,michael.lawson@couchdropdemo.com
chris@couchdrop.io,chris.roy@couchdropdemo.com
```

### &#x20; <a href="#h_01hqrk22020w3cjth772gm2tv5" id="h_01hqrk22020w3cjth772gm2tv5"></a>

### Other Options <a href="#h_01hqrk2202jyh7ckr210pak0hd" id="h_01hqrk2202jyh7ckr210pak0hd"></a>

*Tweak the permission migration further*

| **Send Notification Invitations** | <p>Send email notifications to users when permissions are added. </p><p> </p><p>This option is not supported by all cloud platforms.</p>                        |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Exclude Unmapped Permissions**  | <p>Only include permissions for users that are included in the mappings.</p><p> </p><p>This option is useful for preventing re-sharing with external users.</p> |
| Exception Rules                   | Prevent permissions from being migrated under certain circumstances.                                                                                            |

<br>
