We created a top level site with over a dozen child and grandchild sites. We deployed all the sites and libraries with permissions inherited and then we realized that we needed to break inheritance for every single site for all roles with the exception of a single role (meant to be added for the parent site owner so they could have complete control over the sites and their children). My questions is, wHat is the best way to deploy all these sites that will have the same set of roles but need to have inheritance broken for management reasons? Can we salvage what we have done or should we re-create all the sites and libraries but this time just break inheritance? Can you break inheritance after a site has been deployed? Can you break inheritance on just single role and not all roles for a site? Sorry if this does not make too much sense as I am still somewhat new to SP.

We did this, where we went threw the steps and got the prompt stating if we selected ok it would break inheritance. We selected ok, and then proceeded to remove groups on the site child level.....but somehow that propgated to all the other sites in the collection including the parent. Why is that? Did we not break inheritance correctly?

We created a top level site with over a dozen child and grandchild sites. We deployed all the sites and libraries with permissions inherited and then we realized that we needed to break inheritance for every single site for all roles with the exception of a single role (meant to be added for the parent site owner so they could have complete control over the sites and their children). My questions is, wHat is the best way to deploy all these sites that will have the same set of roles but need to have inheritance broken for management reasons? Can we salvage what we have done or should we re-create all the sites and libraries but this time just break inheritance? Can you break inheritance after a site has been deployed? Can you break inheritance on just single role and not all roles for a site? Sorry if this does not make too much sense as I am still somewhat new to SP. 1. if you want to deploy your sites with broken inheritance you can do it with Feature and site adding receiver progeammatically, but looks like you need to manage them manually so I would recommend breaking inheritance manually as well2. you can rollback your permission to "inherit" mode at any time within the same permissions menu3. You can break inheritance at any time with permissions menu in site settings4. You can't "partially" break inheritance for single role, after you have broken permissions inheritance your site/library just have a snapshot of parent permissions which will not be syncronized with the parent any more, so you can edit broken permissions independently