I came across a problem recently with SharePoint 2013's new Access Request mechanism. It's a great feature, the only problem is, it requests Site Collection admin by default apparently to approve the users that request Access. I have found a work around for this, that will allow site admin's of sub sites to be able to approve/reject access requests for the sub site they are set to receive them for.
There is a list that gets created when an access request happens on a site called "Access Requests", this list doesn't exist till a request happens. Once this happens, you open SharePoint Designer 2013 and navigate to the site.
Once on the site, navigate to the All files menu on the left hand side, then "RIGHT CLICK" the Access requests list which should be in your list and select 'properties'.
Now on the Properties screen, in the Customization Section is a Permissions for this List link. Click this, then you can now set permissions to the users your want to be able to approve Access requests for that site.
This list is generated for each site, so setting this permission only affects that site.
Let me know if you guys found another solution to this or have any questions. Thanks!
I was following your steps above, and created a new group which I gave FULL ACCESS to this list. I then added a user to that group. I also added a link to the list to be Current Navigation of the site. Then I did an IISRESET just to be safe. I then logged into the site using the user that is a member of the group that has FULL access to the list.
But whenever that user tries to access the list using the link on the Current Nav menu, he gets the message "Sorry this item has not been shared with you". Is there some other step that I am missing? If I add the user to the Site Owners/Admin group it all works fine...
This comment has been removed by the author.ReplyDelete
I followed the same steps and I'm able to see pending requests , but nothing is happening when I click on Approve/Reject. and Approve/Reject buttons are enabled in ribbon. am I missing anything?ReplyDelete
The users still have to have full control to the site still. This is just a work around so you don't have to provide SIte collection admin to the users. I haven't tested this with newer builds of SharePoint so not sure if something stopped working, but as renewtx stated above it worked with Full site permissions. Guess I left that part out.ReplyDelete
well I did say Site admin's in my post :P. I've seen approve/reject buttons not work because it has to compile and is delayed, be patient and refresh the page and see if it took hold, also check the site admin permissions to be full on the site level as well.ReplyDelete