SharePoint Item Permission Batch has greatly leveraged SharePoint out-of-the-box capabilities in terms of permission management by offering administrator a convenient place to add or remove custom permission settings for all the items within a SharePoint list simultaneously. In additions, IT administrators are empowered to restore the default permission settings for all the items within a list at one time, which will further alleviate their workload and accelerate the speed of an organization’s daily operation as well.
Moreover, SharePoint Item Permission Batch enables administrators to specify certain users and user groups that will be assigned custom permissions by setting complex conditions based on administrators’ various consideration.

Please note that Item Permission Batch has to be activated before it can be used. For further reference, please see our Product Installation Guide.
Further information is also available in our FAQ.
Feature Introduction
Restore Default Permissions

Clicking this button will undo all changes made by either Item Permission Batch or Permission Workflow, and restore the default permissions settings specified in the list permission settings.

This will also disable the SharePointBoost Permission Workflow.

Once clicking this button a popup window will prompt the administrator to confirm and continue.
Add/Remove Permission

The function allows the administrator to specify whether he wants to remove or add permissions of the users specified. Thus, to remove a specific permission level the administrator has to check what permission level the user has for which item, and then select to remove this specific permission level from the user.
User/Group Selection Process
The User/Group selection process has been modified and improved compared to the previous version. One distinctive difference is that administrators are now able to specify in far more detail which users to include. Item Permission Batch now allows for specific selection of users and groups by Selecting all users/groups or a filter them by:
a) Input of user and group names

As in previous versions, Item Permission Batch provides a box to enter any user or group name. It also allows entering multiple users or groups, and as with the default user selection, the administrator can look up names or check the names entered into the box.
b) Selecting user/group columns, as well as relative lookup fields in this list

As in previous versions, Item Permission Batch provides checkboxes with all User/group columns available. Checking these checkboxes will result in selecting the users which are contained within the selected column. The administrator can also select related columns, if the checkbox to display them is checked. This means that all user/group columns in the list that is looked up from will be available for selection.
c) Looking up users from other lists and filter them based on conditions
The process to select users from another list works in 3 steps:

Specify Selection Criteria Based on Conditions
We have introduced conditions to specify user and items even more precise, and thus providing an even more granular approach. The conditions sections have been added in two sections:
a) For filtering users/groups from other sites
b) For specifying the items that will be affected by the permission settings
a) The process to select users from another list works in 3 steps:
b) Specifying items that will be affected by the permission settings:

By entering conditions, the administrator can specify for which items the permissions are set. The main difference to the user selection process is that these conditions are only based on the current list. There is no reference to other lists possible. Also, the selection process is not based on any associated columns with the user selection, but it takes direct effect.
Item Permission Settings

The Item Permission Settings specify to which items the settings should apply, and what permissions the users should have for these items. To specify the items affected the users can use conditions by clicking "Add Conditions".
After that the level of access has to be set. These permission levels are pulled from the Site Collection permission settings.
The option "Add permission settings" will open a similar pane, so that several different permission settings can be created for similar users.
Example
In a situation where the permissions for each item have been changed manually, changing the permissions on list level will not yield any results. The screenshot below displays the list level settings for the current list.

As the information in this list is confidential the permissions have been changed for each item. With the current setup each users can only view the item related to them, but they cannot make any changes.

This means no matter if you add or remove permissions on list level, for the items with specifically set conditions these changes would not take effect. However, the Administration Manager and the General Manager should be able to make changes and approve them. In the current set up, the administrator would have to change the permissions for every item one by one.
Item Permission Batch can solve this issue by changing the permissions of all existing items in a list. To do so click on the Item Permission Batch link in the list settings.

In the following screen the administrator can specify how to change permissions for the items.
To add permissions for the Administration Manager Item Permission Batch provides the option to look up this information for another list.
Firstly the administrator has to select the site to look up from, and then the list. Here we pull information from the same site, but instead use the list HR Management.

Further the administrator has to specify which User/Group column in this list shall be the source of the user for whom to add permissions, in this case it is the "User" column. The final step requires filtering the information from this column based on conditions. These conditions can be based on any column in this list. Here, the condition to select the Administration Manager would look like this:
[(HR Management).Department]=="Administration"&&[(HR Management).Position]=="Manager"

Then, the administrator has to set what permissions the Administration Manager has. This can be done by simply checking the checkboxes for the desired permissions levels. In this case, the Administration Manager should have permission to Contribute.

Following the permissions settings for the Owner should be set. Here the administrator can just enter his name and specify the permission level he should have.

After the changes take effect, the item permissions have changed, so that now each user has read permission for his own item, while the Administration Manger has Contribute permissions and the Owner has Approve permissions.

Support Languages: English, Chinese.
System Requirements
| Operating System: |
Microsoft Windows Server 2003 x86/x64 Microsoft Windows Server 2008 x86/x64 |
|---|---|
| Server: |
SharePoint Release: - Microsoft Windows SharePoint Services v3 or Microsoft Office SharePoint Server 2007 - Microsoft .NETs Framework 2.0 or 3.0 Note: This product is not compatible with SPS 2003 and WSS v2 |
| Browser: | Microsoft Internet Explorer 6 or greater is recommended for Advanced Administration features |
Release Notes
|
2.1.715.0 Jul 15th, 2010 |
New Feature: - Server license added. |
|---|---|
|
2.1.528.0 Jun 7th, 2010 |
Bugs fixed: |
|
2.0.401.2 Apr 2nd, 2010 |
New Feature: - Offer conditions to determine the users and user groups that will be assigned custom permission settings. |
|
1.17.1209.0 Dec 15th, 2009 |
SharePoint Permission Boost component upgraded. |
|
1.16.916.0 Sep 16th, 2009 |
Bug Fixed: - A column might be invisible to all the users though it was supposed to be invisible only to certain person. |
|
1.16.820.0 Aug 21st, 2009 |
Licensing module upgraded. |
|
1.15.428.2 Apr 28th, 2009 |
New Feature: - Add items’ URLs to certain fields. Bug Fixed: - Removed groups from site user count. |
|
1.12.1226.1 Dec 26th, 2008 |
New Feature: - Fully support customized forms. |
|
1.11.1204.0 Dec 5th, 2008 |
New Feature: - Availability of farm license. |
|
1.10.1125.0 Nov 25th, 2008 |
Bug Fixed: - User fields could not be assigned permission in some cases. |
|
1.9.1121.5 Nov 21st, 2008 |
Bugs Fixed: - Some views were hidden though they should be visible in those cases; - Improve performance for batch permission settings. |
|
1.8.1104.0 Nov 4th, 2008 |
Bug Fixed: - Resolved the error happened when a view had an empty title. |
|
1.8.1031.1 Oct 31st, 2008 |
New Feature: - Support column permission for anonymous; |
|
1.7.0.3787 Oct 15th, 2008 |
New Feature: - Support assigning column permissions to user/group columns in a list. Bugs Fixed: - Resolved the error happened when users logging in as anonymous; - User lists were too long and no new line when assigning permissions to many users. |
|
1.6.0.3709 Oct 10th, 2008 |
New Feature: - Allow assigning column permissions to all users except specified ones. Bug Fixed: - Fixed errors in page title and description. |
|
1.5.3.0 Aug 18th, 2008 |
Bug Fixed: - Resolved the errors happened when inserting an image into a new item, but failing to save the new item. |
|
1.1.0.0 Jul 2nd, 2008 |
Initial Release |
Purchase FAQ
An end-user is defined as any user who has access to, or has accessed any site in your Site Collection/Farm at any point in time, either directly (e.g. signing in) or indirectly (e.g. assigning him a task). Once a user has accessed a site in the site collection or the farm where the product is used, he is counted, regardless of whether or not this user is active on the specific site where the product is used. For example, while you may only have 50 users who would need to use the product on Site A in the site collection, there are 360 users accessing Site B (including the 50 accessing Site A), making a total of 360 users with access to the site collection. Since Site A and Site B are in the same site collection, you would need to purchase a license for at least 360 users. SPB licenses increase in increments of 100 users, so if there are 360 people who have access to the site collection, you will need to purchase a 400 end-user license.
If you would like to place an order with a PO, please contact sales@sharepointboost.com.

