Permissions are defined in the Model Library. You simply set the required unique permissions directly on files and folders.
| Implementation of file and folder level permissions |
- Set the required unique permissions directly on files and folders in the Model Document Library. When the “Migration” Job runs, the assigned permission are copied across to the destination.
|
- Permissions from the source SharePoint location are copied into the
FileProxy column [Source permissions (Text)] and serves as information to use in context when new permissions are applied.
|
- Support for: SharePoint groups, AD groups, AD users, standard and custom permission levels.
|
- SharePoint groups must exist in the destination site. in other words, no SharePoint groups are copied across. However, Customs permission levels are dynamically created on the destination.
|
- The PreMigration job can verify that the referenced SharePoint Groups are defined on the destination site and if not the issues are reported to the Migration Issues List
|
- If any folder has permission issues then no files are migrated.
|
- Individual files havening permission issues or any other issue like content-type etc. are not migrated. The individual file issues are reported to the Migration Issues List.
|
- File permissions are only copied across when the file it self is migrated. So, changing then file’s permissions on the Model library does not trigger the permissions to be incrementally updated on the destination. You can explicitly set the file to “ReMigrate” to force the file to be migrated including permissions.
|
- Existing permission on the destination files and folders are replaced by the permission defined in the Model.
|
Last modified:
6 February 2024
