Hi,
We are about to roll-out an implementation of SharePoint 2013 on-Premises which is managed for us by a 3rd Party via a Private Cloud.
As far as roles and responsibilities go, our provider will provision Site Collections - whilst we manage sites within those.
To this end - the provider will provision site collections per operational company per "type" ie :-
https://siteroot
-- https://siteroot/sites/ukteamsites
-- https://siteroot/sites/ukprojectsites
-- https://siteroot/sites/usteamsites
-- https://siteroot/sites/usprojectsites
...etc..
On this basis, they will manage the content databases that may need to be created in which to host a new site collection.
These top levels are merely "buckets" in which we then create our sites (of which we've decided to limit depth - but go very wide) :-
-- https://siteroot/sites/ukteamsites/teamsite1
-- https://siteroot/sites/ukteamsites/teamsite2
-- https://siteroot/sites/ukteamsites/teamsite3
Each of these sites will have unique permissions because they are - to all intents and purposes - separate logical containers much like you'd typically use SiteCollections for (as you do within O365).
Clearly, on observation - if I'm within /ukteamsites/teamsite1/_layouts/15/groups.aspx - I can see an unmanageable list of groups since every subsite unique groups "bubble-up" through the site collection.
No matter where I am - I can see the groups listed for the other sites ... and this is unwanted behaviour.
Is there a way to modify this (without resorting to separate Site Collections) so that - if I'm within teamsite1, I only see:-
teamsite 1 members
teamsite 1 owners
teamsite 1 contributors
etc ... and NOT additionally see the members, owners and contributors for ALL other sites in the site collection?
I can manage the groups to hide membership ... but the groups still show. I anticipate we will have hundreds (even thousands) of "sites" which need to be administered individually and separately without inheritance from the top level site collection ..... but we don't really want to resort to standing up separate site collections for this?
Thanks
Steve