Breaking Inheriting Permissions and creating groups
Hello everyone, I am trying to control access to folders from specific user. So I created a library and "stopped inheriting permissions", my plan was to create groups with different access levels and add different users within. But as I was about to do this, I ran into an issue, I realized that groups are created at the site level and because of this, the groups will also have access to the other Libraries I have within the same site...which is something I do not want and is risky. The only option I see so far is to add individual users into the Library and then restrict each folder to each user individually. But the issue is that this will not work in the long run. Is there any other way to do this that anyone is aware of? Thank you all. The image below shows I am only able to a
Inheritance--problems caused by bidirectionality
Is there any way to inherit permissions downward to child subsites without also generating permissions upward to the parent site? when a group must be given access to a subsite? There are multiple scenarios when (a) it is administratively necessary to have uniform permissions cascade from one site to all subsites, while also (b) having some unique permissions on a child site. For example, I might need to add a new security group, or to remove a security group, from one level below the root site down through all subsites below that level; I might also need to provide a specific security group with access only to a few subsites or lists. With bidirectional inheritance as it appears to exist now, if I am going to give a specific security group access to only a few subsites or only a few lists, then the only way to do that is to break inheritance on those subsites or lists. Once I do that, I can no longer add/remove a group to the entire tree. Is there any solution to this?Disallow Inheriting Permissions at Site Level to Site Collection Level
I have an issue wherein not all Site Owners are advanced users and managing permissions is a bit of a learning curve that for some is relatively steep. In our set up, we have a Site collection with hundreds of sites. Want: Is it possible to prevent the Delete Unique Permissions button from being enabled at a Site/SubSite level - or available only to Farm Admins? To help explain the scenario: Site Collection: myHub (for example) - Permissions set for this collection (myOwners, myMembers myVisitors) Site: mySite (myHub\mySite) - Permissions set for this site (mySiteOwners, mySiteMembers, myVisitors) Site: myOtherSite (myHub\myOtherSite) - Permissions set for this site (myOtherSiteOwners, myVisitors) Now, I currently am able to go to the Site Settings of mySite and delete unique permissions (basically scarpping anything I've done to mySite with regards to unique permissions) and as a result, mySite and myHub would not have the same permissions, managed at myHub (myOwners, myMembers myVisitors) I want to prevent that from happening. I do NOT want any site owner (only Farm Admins) to be able to inherit permissions from the Site Collection - as there is never ever ever a business case to do so. By having this functionality available (and not fully aware Site Owners), it simply results in support call after support call stating, "I can't do anything with my site anymore..." which inevitably is because they are no long Site Owners of their site - from inheriting from the Site Collection. Thanks in advance.
