07-21-2019 09:04 AM
07-21-2019 09:04 AM
The other day, I had to give access to a colleague to a repository inside of a document library. Since he didn't have access to the Sharepoint Online site, I simply "shared" the repository with him. In addition, he didn't nor should have access to anything else ... and it worked perfectly :)
The other day after adding a new group of users (Azure AD group) as site members, I noticed they didn't not had access to the previously shared repository. The access rights were set, for the new AD group onto all the other repositories, at the exception of the previously shared repository. On the access rights panel, SharePoint indicates that it had " unique permissions ". From my point of view, sharing a repository should not block a change of access rights at the top level of the site.
Is this behavior normal ? Any ideas on how to fix this ?
07-26-2019 09:59 AM
By "repository" I assume you mean a folder?
If you clicked the dots next to the folder >> Share, then the user should not even have access to the site itself (he/she isn't even added in the Visitors group), but only to this particular folder via the link sent through the sharing.
I've tested your scenario on my tenant, and it worked fine.
User only has access to this particular folder, and the Group can see everything.
07-28-2019 11:27 AM - edited 07-28-2019 11:28 AM
Thank you very much for your answer.
Yes, by repository I did mean a folder :)
When I follow the different steps indicated in your message, I have the same result. That's were my concern is : sharing a folder with someone seems to break rights inheritance. If I grants a new access at the site level, it remain absent on those previously shared folders. However, the new access isn't valid on all the non shared folders. I wanted to know, is this normal ? Has anybody experienced this scenario ?
07-28-2019 02:26 PM - edited 07-29-2019 09:31 AM
Quite normal, that’s the way SharePoint does permissions. Everything in a site starts out the same way, but once you change a list, or a folders permission, it breaks the permission off. It copies it’s current setting, but after that you have to maintain it on your own
This is why people try to discourage breaking inheritance, it can be a pain to manage. Adding people to groups already defined for the list/library work, but you’ll always have to add individuals or new groups yourself
08-01-2019 09:59 AM
Thank you very much for your different answers. It is very clear.
I found this a bit surprising since this sharing functionnality is accessible by end-user who may not be aware of this topic. At the end of the day, I would have hoped for a functionnality where "sharing" would add an extra-access without Breaking inheritance.