This article describes how to use the Copy Object Permissions Wizard in order to match principal and group permissions on two different SharePoint objects.

Copy Object Permissions Wizard

This article explains how to use SPDocKit to easily copy SharePoint permissions from one object to another.

The Copy Object Permissions Wizard enables you to copy the permissions between objects that are a part of different site collections or even different web applications.

Please note!
Source object's permission inheritance must be broken in order to use this wizard. Source object permissions will not be affected by this wizard. Based on the options selected in the wizard, the destination principals and/or groups can lose all previously assigned permissions or acquire additional permissions. SharePoint groups of the target site collection can also be changed, which affects not only the target object but also all other objects to which the group is assigned.

Wizard Scope: web application, site collection.
Supported source SharePoint Object selection: all object levels from site collection root site to list item.
Supported target SharePoint Object selection: all object levels from site collection root site to list item.

  1. Navigate to Permissions Explorer and select the source object in the object tree. Select the Copy Object Permissions options in the Manage ribbon.

  2. In the Target selection step select the target SharePoint object.

  3. Depending on the previous source and target object selection, the Configuration step offers a couple of options.

  4. Source and target objects are a part of the same site collection.

    The Keep existing target object permissions (role assignments and SharePoint group memberships) option is available. If checked, all of the target object permissions are preserved and new permissions are added to existing groups or principals. If not checked, all target object permissions are removed and the source permissions are copied.

    Options Create SharePoint groups and Create missing permission levels are disabled since they are only applicable in case of different site collections.

    If the target object inheritance is not broken, the following message is displayed: The target securable object currently inherits permissions from its parent. Permission inheritance will be broken in order to apply new role assignments.

  5. Source and target objects are a part of different site collections.

    The Create SharePoint groups option is available. If checked, missing SharePoint groups are created on the target site collection with the same members as in the source group. If unchecked, no new groups are created.

    The Create missing permission levels option is also available. If checked, missing permission levels are created on the target site collection with the same base permissions as in the source permission levels. If unchecked, the permission levels are not created and therefore can not be assigned to groups or principals.

Please note!
If the source site collection and the target site collection have SharePoint groups with the same name and different members, and the Keep existing target object permissions option is checked, existing members in the target group are preserved and new members from the source group are added. If the Keep existing target object permissions option is not checked, the target group members are removed and source group members added.

If the source site collection and the target site collection have Permission levels with the same name but different base permissions, the target permission level will not be changed, and it will not be added to any principals or groups. The following message appears in the Preview window: Permission level [permissionLevelName] already exists on [targetSiteCollection] with different base permissions and will be skipped.

The Preview step shows the changes that will occur in the final step.

In the Apply Changes step, all changes are displayed as they are applied. It is possible to save the log for later reference by clicking the Save Log button. The changes are also saved in the SPDocPerm event log.