SharePoint Column/View Permission can hide SharePoint columns/list views and make SharePoint columns READ-ONLY. SharePoint default permission scheme does not define permissions on SharePoint columns/list views. Based on your configuration of Column/View Permission, it can implement SharePoint column permissions and SharePoint view permissions in lists dynamically.
SharePoint Column View Permission allows SharePoint Administrators to hide SharePoint Columns or set them as read-only to certain viewers.
1. SharePoint columns can be hidden to some users/groups if you set INVISIBLE columns for them:
- The contents of this column will be HIDDEN to him/her in item display form or edit form;
- List views which contain SharePoint hidden columns are also invisible to him/her and cannot be selected by him/her in View Select Menu.
2. SharePoint users/groups have NO EDIT permission to some columns if you set SharePoint read only column:
- The contents of this column will be read-only to him/her in item edit form;
- List views, which contain this SharePoint read only column, cannot be switched to datasheet view or edited in MS Access, as the menu items in Actions Menu will be hidden to him /her.


SharePoint View Permission allows SharePoint Administrators to set permission on SharePoint Views, making them read-only or invisible to certain users.
1. If SharePoint user has NO READ permission to some list view, the list view will be hidden in View Select Menu;
2. If SharePoint user has NO EDIT permission to some list view, the view cannot be switched to datasheet view or be edited in MS Access (the menu items in Actions Menu will be hidden to him /her)


SharePoint Column View Permission can also make items’ attachments invisible or read-only to certain people.
Why Did We Build It?
SharePoint column permission and SharePoint view permission is highly expected by many IT managers and developers; because permissions on column/list view provide another permission control dimension. SharePoint 2007 doesn’t provide permissions on SharePoint columns and SharePoint list views directly; but we can implement SharePoint column permission/list view permission in representation layer by overwriting default control templates. Even if you can bypass this way through API invoking, it is still useful to those who eagerly need column permission and list view permission.
Firstly, SharePoint Column Permission
SharePoint Column Permission can make column invisible or read-only to certain people. For instance, there is a list contained employee profiles. Everyone can view the basic information like name and ID. However, only the accountant has the SharePoint column permission to salary, while administration staff has permission to all columns except salary column.

Invisible Column
There are three view types: Public View, Accountant View, and Administration View. One cannot access to this view also without permission to a column belonging to a certain view.



In list setting page, click "Column permission setting" and enter into the standard SharePoint column permission setting page.

The following is an example of giving SharePoint column permissions to ordinary staff like Tom. Add his name in "users/groups" editor box. Select and move "Address", "Cell Phone No.", "Salary", and "Leader" column to the right box. These columns are read-only to Tom.

SharePoint Column permission setting to accountant is the similar setting to ordinary staff. Jerry is an accountant who has permission to salary column.

Give Herny, an administration staff, corresponding SharePoint column permission.

Now, Tom can only choose "Public View", Jerry can access to "Public View" and "Accountant View", while Herny can view items in "Public View" and "Administration View"
In display form, Tom cannot see "Leader", "Address", "Cell Phone No." and "Salary" column.

Read-only Column
The information in employee profiles is input by different departments with corresponding SharePoint column permissions.
For instance, Jerry, an accountant, can only edit the salary column of each employee. Enter into the accountant setting page. Choose and move all columns except "Salary" to the right box. All the columns except “Salary” are read-only columns to Jerry.

In Edit form, Jerry can only edit salary column.

If current view contains read-only column, the "Edit in Datasheet" menu item in Action menu will be hidden to avoid users editing read-only columns.

There is another list containing Financial Reimbursement, Everyone can view the basic information such as Employee Name, Timing, Use to Describe and Account.

Attachment permission
Jerry, as an accountant, wants to create an item with an attachment, which should be invisible to ordinary staff like Tom and read-only to administration staff like Herny.

Then we can set the SharePoint column permission for Tom and Herny.


After these settings, Tom cannot see the attachments, and Herny can only view the attachments while not edit the attachments.


Secondly, SharePoint View Permission
SharePoint View Permission can make list view invisible or read-only to certain people. As the instance above, there is a list containing employee profiles. Everyone can catch the basic view like “Public View”. However, only the accountant can have SharePoint View Permission to “Accountant View”, while administration staff has access to all views except salary column.
In list setting page, click "View permission settings" and enter into View permission settings page, then click the “View Permission Setting” button to edit the SharePoint view permission.

The following is an example of giving ordinary staff like Tom SharePoint view permissions. Add his name in “users/groups” editor box. In “Choose read-only views” list, select "Administrator View" and "All Items" to the right box. These views are read-only to Tom. In “Choose invisible views” list, select “Accountant View” and “Leader View”, and move to the right box. These views are invisible to Tom.

Setting view permission to accountant is similar to setting for ordinary staff. Jerry is an accountant who has access to accountant view.

Give Herny, an administration staff, corresponding permission.

Now, Tom has read-only permission to “Administrator View” and “All Items”, and cannot see "Accountant View" and “Leader View”.
Jerry has read-only permission to “Administrator View”, but cannot see “Leader View”.
Henry cannot see “Accountant View”.
Invisible View
In display form, Tom cannot see “Accountant View” and “Leader View”.

Read-only View
The information in employee profiles is input by different departments with corresponding permissions.
For instance, Jerry, an accountant, can only edit the accountant view, but has read-only permission to “Staff View” “Public View” and “All Items”.
In display form, Jerry can only edit under the accountant view, but cannot edit under staff view.

Top