Posts Tagged ‘users’

MetaVis Platform Features Overview: Browse list or library permissions and copy selected list permissions between lists

April 8, 2011

SharePoint lists by default have their permissions inherited from the sites where they got created. However it is possible to break list permission inheritance and set up unique permissions for the specific list. In this case list permissions will not be changed in case someone will change site permissions however unique users or groups could be added to the list permissions.

 

MetaVis Migrator and MetaVis Change Manager support copying or unique list permissions between SharePoint sites. This time we added a function to display list permissions in the MetaVis Content Viewer and copy individual permissions between lists, sites and site collections.

 

Right click on a list, select Objects and then Show Permissions menu item to browse list permissions.

 

 

Users can copy and paste or drag-and-drop permissions records from this Permissions Viewer to the other list in this or other SharePoint site.

 

Also note the little icon on the Permissions Viewer toolbar that is an indicator that the list has permissions inherited from the parent site. Clicking on this button would break or restore list permissions inheritance.

 

 

Advertisements

MetaVis Platform Features Overview: Bulk user mapping to add or replace domain in login names

March 8, 2011

Many if not all SharePoint objects have user accounts associated with them. They could come in the form of basic item or document properties like Created By or Modified By. The other example is the value in Person or Group field. Users could also be members of SharePoint security groups or object permission records.

One of the common problems that arise when people copy SharePoint objects or the whole site collections between active directory domains is to change account information when copying users. For a long time MetaVis Migrator used to have an ability to specify user mapping when performing copy operations. Each Copy Wizard to copy items, lists, sites, permissions or user groups includes the controls to provide user mapping

User mapping should be provided in the form of CSV file with a row per user mapping. Each row should specify account name is the source and target environments separated with comma.

While this approach works well in majority of the situations it is often hard to compile user mapping file if environments contain hundreds if not thousand user accounts.

To cover the situation with bulk user mapping, MetaVis Migrator added the ability to provide user-mapping rows using wildcard specifications like on the picture below

In addition to this, the wildcard specification could just add a domain to the account that does not have domain in the source environment

The later mapping could be user to map user accounts from FBA environments or from non-user fields like text field or MS Office Authors or Last Saved By fields.

It is worth to note that the wildcard records could be provided in the mapping file in addition to the real account mapping. This technics provides the mechanism to specify default values to the user mapping in addition to the direct mapping of the account that have more changes in the source and target environment than just domain change.