Please note that Permission Workflow has to be activated before it can be used. For further reference, please see our Product Installation Guide.
Please note: Column/View Permission settings will not take effect for site collection administrators, System Account and for users granted Full Control by the permission policy in Central Administration.
Further information is also available in our FAQ.
1. Column Permission Feature Introduction
1.1 Column Permission
This function lets the administrator globally enable or disable the Column Permission settings configured with Column Permission in this list.

1.2 Permission Settings
The Permissions Settings section gives the administrator an overview over all Column Permission settings already set up. Each settings part can be deleted, enabled or disabled. The status field displays whether a settings part is enabled or disabled. To edit a Column Permission settings part click the name of the settings part,this will open the settings page for the Column Permission settings part.
To add Column Permission settings, click. 
1.3 Advanced Settings
The Advanced Settings section gives the administrator option to decide if the read-only columns can be edited on the object-model level, or by applications which use object-model.
To prevent editing read-only columns on object-model level, select "No" option; otherwise, select "Yes" option.

1.4 Import or Export
Import/Export permission part function is based on XML files.

To import settings click the Import button. In the popup window, administrator can either paste the XML file contents into the designated area, or browse for a file and upload it. To confirm the XML file importation click the OK button. To abort importing the specified permission settings, click the Cancel button.
To export permission settings click the Export button. A popup window will open and display the XML file contents in the Edit area. The administrator can then save the settings to any location and thus make it reusable in other lists.
1.5 Add Column Permission Part
1.5.1 Permission Settings Name
Name each Column Permission settings part. The settings part will be displayed with its name in the Permission Settings table in the main settings page for Column Permission.
1.5.2 Include/Exclude People
The User/Group selection process is divided intwo parts: Include People and Exclude People.
The Include People section lets the administrator decide if he wants to include all users, or if he wants to select a small group of users based on criteria that he specifies.
The Exclude People section helps the administrator to decide which users are excluded from the permission settings.
Both Include People and Exclude People sections contain the same components.
Column View Permission allows selecting all users or selecting specified users by filtering them as follows:
- Including anonymous users
- Input of user or group names
- Selecting user/group columns, as well as relative lookup fields in this list
- Looking up users from other lists and filter them based on conditions
a) Anonymous Users

This allows administrator to include anonymous users in the permission settings.
b) Input of user and group names

Column View Permission allows entering multiple users or groups; administrator can look up names or check the names entered into the box.
c) Selecting user/group columns, as well as relative lookup fields in this list

This function is provided to assign permission to Person or Group columns which present users or groups.
Checking checkboxes next to the Person or Group columns will result in selecting the users which are contained within the selected column. This selection will filter the values in the column specified with the logged in user. The permissions are only set for items associated with the currently logged in user, but will not affect any other item.
The administrator can also select Person or Group columns from related list if the checkbox next to "Also display User Group columns in other lists related to Lookup columns in this list"is checked. This means that all user/group columns in the list that is looked up from will be available for selection.
d) Looking up users from other lists and filter them using conditions

The process to select users from another list includes 3 steps:
- Specify the list to look up from. To do so, the administrator has to firstly select the site on which the list is located. Note that only sites in the same site collection are available.
- Specify the User/Group columns that will be used to specify the users. These are to be selected through checkboxes, similar to the User/Group column selection in the original list. The difference is that all the users are pulled from the column regardless of the user who has logged in. Thus the settings will be the same for all items. Also, related columns are not available to select in these settings.
- A final step is the ability to filter a selection of users using conditions.
1.5.3 Conditions
Two conditions types are provided in settings page, Basic and Advanced.

The Basic conditionshelp administrator to easily configure conditions.

The Advanced conditions provide more operators and functions to implement elaborate conditions beyond basic conditions.
1.5.4 Form Permission Settings
Column View Permission allows the administrator to specify what columns are accessible in what way for each form. Administrator can set columns hidden or read-only in New Item Form, Edit Item Form and View Item Form.
Column Permission and View Permission are working closely together. This means that columns hidden from certain users will have to be removed from a view if these users should be able to access this view. If a view contains these columns it will not be accessible by users.
2. Column Permission Example
Here is a list that keeps confidential HR information.

The screenshot above illustrates this issue; here some information is included that normal employees should not be able to view or change.
To change this behavior, navigate to the Column Permission Settings. To do so, enter the List Settings page.
Note: To configure the Column View Permission, you should be the member of site or site collection owner, or have Full Control permission on the list.

Here is a list that keeps confidential HR information. 
Firstly specify the name of the permission part; here it is called "Administration".

Here, all SharePoint users except HR department should be limited to view or edit the columns so, in the Include People section, the radio button is to be set to "Select All Users".

To exclude account, tick "Exclude People" checkbox.
Here we exclude employees in the HR department. To do so, select
Then select HR Info list from HR site.

After that, a column has to be selected from which the users or groups are pulled from. The "Account Name" column contains all the users in the company; therefore this information has to be filtered. For filtering this information, Column Permission provides condition settings. The condition in this case is:

This condition specifies that only users working in the HR department will be selected.
To complete the settings you have to specify what permissions the users should have for which form.

Here we set columns hidden or read-only for each item form.
After all settings have been made, confirm by clicking OK. Please note that you also have to click OK in the Column Permission main settings page to confirm any changes made.
Log in as a user who is not working in the HR department. The New Item Form now does not display any column to edit, it is completely empty.

In the Edit Item Form, only the columns set as read-only are displayed, all others are not shown anymore. The columns displayed cannot be edited at all.
Columns which are set as hidden in View Item Form cannot be viewed.

As Column Permission is linked with SharePointBoost's View Permission, views containing columns that are hidden from users will be not accessible.

3. Hide columns in Alert Me email
Column/View Permission version 3.0 and above now support hiding columns in Alert Me emails.
To use this feature, in central administration, activate the "Column Permission for Alert Me" feature for web applications.
Once the feature is activated, columns will be automatically hidden in emails based on the Column Permission configuration.

Note: after installation or upgrade of Column/View Permission version 3.0 or above, Timer job service should be restarted on each server of farm.

4. View Permission Feature Introduction
4.1 View Permission
This function lets the administrator to globally enable or disable View Permission settings configured in this list.

4.2 Default View Permission Level
This function defines the default behavior for View Permissions. If the default level is set as "Hidden" then existing and new views will be hidden by View Permission settings unless the administrator specifically set these views full access or read-only. Setting the default to be "Visible" will thus allow all new and existing views to be accessible by default. Also, administrator can set permissions for each view in the Permission part.

4.3 View Permission Redirect Page
These settings give the administrator the option to configure notifications if views are unavailable to users. Check the "Use redirect page" to use this feature. If activated, any users without sufficient permissions will be directed to a page presenting him with the following options.

There are four messages that can be configured. However, for each message a default message is preset.
- The "View unavailable message": This message will be displayed if the user does not have sufficient permissions to access the view selected.
- The "All views unavailable message": This message will be displayed if the user does not have sufficient permissions to access any view for this list.
- The "'Go to view' button text": This message will be displayed on the 'Go to view' button, to direct the user to the next available view.
- The "'Return to homepage' button text": This message will be displayed on the 'Return to homepage' button to direct the user from this list.
4.4 Import or Export
Importing and exporting permission parts for View Permission works in the same way as for Column Permission (see above).
4.5 Add View Permission part
To add view permission settings, click
in view permission main page.
4.5.1Permission Settings Name
Specify a name for the view permission settings part.

4.5.2 Include/Exclude People
The User/Group selection allows administrators to specify which users to include or exclude from the selection process. In "Include People" section, administrators have the option to:
- Include/exclude anonymous users
- Enter user or group names
- Look up users from other lists and filter them using conditions
Selection parts for View Permission functions in the same way as Column Permission (see above).
4.5.3 View Permission Settings
In the View Permission Settings, administrator can specify the permission level that users will have for each of the views in a list.

The Access Type defines whether the view should be fully accessible, read-only (Disable Edit View), or hidden for the selected users. (Please note that setting a view as read-only will mean that no items in the list can be edited or deleted unless the user has the appropriate permissions. Also, the "modify this view" option in the Views dropdown menu will not be available for thisview).
Administrator can check "Disable create view" option to prevent users from creating views in the list, including public view and personal view.
Administrator can also decide which ribbon buttons are not available for users by setting the iconsto "disabled" status.
4.5.4 Default View
In the Default View settings, the administrator can specify the default view for selected users in "Include People" section.
After configuration, the logged on users will visit the specified default view when they try to access the list.

5. View Permission Example
In companies there is information that should only be accessible to certain people. So only staff in the HR department has to be able to read and modify private information of employees. Other employees should not be able to access this kind of information.
The views containing private information should be hidden for all users except HR department.
A way to achieve this goal is to define views that include the necessary information for its target audience, and then restrict the access level with SharePointBoost View Permission.
First, create a view that will be accessible for all employees. This view is called "General Info".
Then, create another view for HR staff only; this one is the "Detail Info".
The "General Info" view includes no sensitive information, while the "Detail Info" view displays all columns for the HR Department. To set permissions for these views, navigate to the "View Permission" settings page.
Note: To configure the Column View Permission, you should be the member of site or site collection owner, or have Full Control permission on the list.

Note:
In the List Settings page click on the "View Permission" link to be directed to the "View Permission" general settings page.
The administrator has activated the Redirect Page, so that users are informed of their choices when they navigate to a view for which they do not have permission.
Then navigate back to the View Permission main settings page, and click "Add View Permission Settings". The administrator creates a settings part that allows users access the "General Info" view, while denying access to other views that contain confidential information. This settings part is called "General View".

Then administrator has to specify which users will be affected by these view permission settings. As all employees should be able to access this view the administrator just selects the "Select all users" radio button.

For "Exclude People" section, employees working in the HR department should not be affected; they are excluded using the following condition:

Now the administrator has to select which views are available to the employees, and which permissions they have for these views.

Also, administrator limitsemployees to create views both public and personal by checking "Disable create view" option.
In this view permission part, administrator wants employees to visit "General Info" view by default.

Then, the administrator still has to set up the view permissions for the HR department. Firstly, again, create a new View Permissions settings part. Name it "Detail view".

Then, select which users to include. Here the view permission is only for HR department, so, select "Select Only the Following Users" option.
And then, select the employees working in the "HR" department using the following condition:

Now, the administrator has to specify what access type the HR employees should have for each view.

Because the administrator wants the HR employees to visit a different view by default, select here"Detail Info" view in "Default View section".

Logging in as Mike from the Development department, only the "General Info" view is available. Also, the actions in ribbon are disabled.

On the other hand, if Laura from HR department logs in, she visits "Detail View" by default. She can access all views and has permissions to click ribbon buttons.

6. Column/View Permission API
Column/View Permission 3.0 publishes an Application Programming Interface (API) to be compatible with other applications.
For more details, please refer to Column/View Permission 3.0 API Documentation.
7. Column/View Permission Web Service
With Column/View Permission 3.0, the following web services methods are limited by Column/View Permission configurations.
| Service |
Methods |
Description |
| Lists (Lists.asmx) |
AddAttachment
DeleteAttachment
GetListAndView
GetListItems
UpdateListItems
GetListItemChanges
GetAttachments
|
Methods for working with Lists and List Data |
| Site Data (SiteData.asmx) |
data from sites or lists
GetAttachments
GetListItems
|
Methods that return metadata or list |
| Views(Views.asmx) |
AddView
DeleteView
GetViewCollection
GetViewHtml
UpdateView
UpdateViewHtml
UpdateViewHtml2
|
Methods for working with list views |
To use Column/View Permission on web services, you need to install Column/View Permission Web Service on each web front end of farm.
For further information on how to install Column/View Permission Web Service,please refer to Column View Permission Web Service Installation Guide.
Top