SharePoint 2013 single page design permission_html/css_WEB-ITnose

This article introduces the use of SharePoint, disconnecting single page permissions, giving users editing permissions, and the problems encountered in the operation. I hope it can be a reference for those who need it.

1. First enter the page library, find our page, and enter sharing, as shown below:

2. Select Advanced in the pop-up window, as shown below:

3. When entering the permission editing page, first disconnect the permission inheritance of the current page, as shown below:

4. Then check all inheritance Delete the permission, as shown below:

5. Then click Grant Permission, which is authorization, as shown below:

6. Follow my instructions According to my understanding, the user has access rights to the site and edit rights to individual pages, so he can personalize the page. However, when adding some WebParts, the following error message appears:

---------------------------Message from webpage --------------------------- A Web Part or Web Form Control on this Page cannot be displayed or imported. You don't have Add and Customize Pages permissions required to perform this action.

7. After trying for a while, I found that no matter what permissions I gave to this page, it would not work, even full control would not work. Therefore, I think the permissions are not in the page, but in the site permissions. So, I create a new group "Custom";

8. Then add permission levels to this group, as shown below:

9 , add the user to the group, as shown below:

After adding the user to the group, I found that the page can indeed be designed, and other pages cannot be designed; therefore, I judged that individual page authorization, in addition to the design of the page permissions, you also need to have Add and customize Page permissions on the site. Moreover, after giving the Add and customize page permission to the site, you will not have the editing permission for all pages because there is no manager list permission.

Summary

SharePoint’s permission control does have dependencies in some places, especially separate authorization is more obvious, for example, you have permission to a certain page , it may affect access due to lack of permissions on css. I believe that with continuous practice, our understanding will become clearer.