Give site owners a consistent access request experience
The request access process is inconsistent across the product. When a user requests access to a site he or she is not a member of, the site owner has an easy time granting the user the appropriate level of access by clicking the ... context menu and assigning the user to a group.
If a user requests access to a library with unique permissions from the parent, the site owner can only grant the user an explicit permission level even though there are groups in place that govern access. Giving a bunch of users direct access to an object just isn't maintainable. Go get around this, the site owner has to decline the request and go add the user to the appropriate group through a series of clicks and hops.
I would like to see the experience for any object request treated the same. Any groups that govern access to the object are presented in the access request to the site owner as well as explicit permission levels.
A bonus to this would be to set the default permission level to Contribute versus Edit.
6 comments
-
Dirk B.
commented
This is soemthing I would like to see improved!!!
It should be possible to approve an access request on a specific Library or page using the groups of the site.
actually I have to decline the library or page request and have to add the user manually to the group.The current way is absolutely a night mare as you will loose control who has what permission on what.
It is currently a time consuming and painfully process.PLEASE WORK ON TO IMPROVE !!!!
-
Tom Braman
commented
I just noticed that this request is being addressed by Microsoft per another request. See https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration/suggestions/15255873-optimize-access-request-settings-for-site-owners
I'm moving my vote over there...
-
Tom Braman
commented
Agree fully with Eric. The whole access request process needs attention. We use it only so end users can request access, and instead do all permissions via the Site Permissions page (/_layouts/15/user.aspx). That creates a mess of pending requests and external-user invitations on the Access Requests page (/Access%20Requests/pendingreq.aspx) that we just leave alone to expire (accepting them would often put users in the wrong groups; declining them would send the wrong message because we are actually 'accepting' them by granting access via the Site Permissions page.
I'd love to know if/when Microsoft decides to prioritize this, as I could provide a number of real-world problems with the current interface and at least an equal number of solutions that would make it useful for end users, including site owners.
-
Eric Alexander commented
It is a pain yes, but I'd rather let site owners manage their access that IT support requests
-
Star D.
commented
I'm out of votes, but I like this suggestion.
-
Ken G
commented
I turn off access requests for every site I create because it is such a pain.
