Use the open-source SharePoint permission extension plug-in to control the permissions of SharePoint lists!

Recently, you need to control the permissions of the Sharepoint list in the project. For example, the contract information is maintained by each department and only the data maintained by yourself can be viewed. This is mainly achieved through the list view, however, the list view has relatively weak permissions, making it difficult to meet Personalized Requirements. Codeplex found that a Sharepoint permission extension plug-in can meet the requirements. This plug-in can implement the list content type permission, list field permission, view permission control, and so on, the following describes the deployment of this plug-in. The download location of this plug-in is as follows:

Http://sppex.codeplex.com/, download the latest WSP file.

Decompress codeart_permissionex_1.51 and place the package on the server of the SharePoint management center, for example:

Open the SharePoint 2010 management shell (run as Administrator) in the SharePoint management center and enter

Add-spsolution c: \ deloyment \ Sp \ codeart_permissionex.wsp press enter, for example:

After the operation is successful, choose SharePoint Management Center> system Settings> farm management solution, for example:

 

 

Deploy codeart_permissionex.wsp, for example:

Enter the website of the front-end server of SharePoint and activate three extensions in the website, for example:

After the configuration is complete, three additional settings will be added to the website list settings: content type permission settings, view permission settings, and field permission settings, such:

Content permission settings: You can set project and folder access permissions, such:

View permissions can be set to view the permissions of a specified person and a specified group, specifically:

You can set the permission to view and edit a list field, for example:

 Through the deployment of this plug-in, you can further improve the list permission function to better meet Personalized Requirements. during deployment, you must note that this method is performed in the form of a server farm, it can be distributed to all web front-end servers without one deployment. Therefore, the request of the Web Front-End Server is terminated. It is best to deploy the server when it is idle to avoid affecting normal operation.

 

this blog is original in software life. You are welcome to reprint it. For more information, see http://www.cnblogs.com/nbpowerboy/archive/2013/05/13/3076307.html. Assume or use it for commercial purposes, but you must keep the signed software life (including links) in this article ). If you have any questions or authorization negotiation, please leave a message for me.