Description

Currently we have maintained around 100 different SAP-Systems within our Central Foundation. We have the user requirement that the user need to be separated and should not see all existing SAP-Systems. For that reason we have two different approaches which we could follow. First one is the creation of different collection sites and create a configuration on each collection site for this users. Second one and more preferred one is the creation of different sub-sides which include a Winshuttle Foundation Team Site. For a first test i created a subsite (called XYZ) which and configured that one. This subsite inherites all configurations of my collection side and I am able to connect with my studio client to this dedicated subsite as well.

Are there any recommendations from Winshuttle either to use a collection side or use a subside? my prefer is to use a subside as this inherits all defined polices, etc... from my master collection side.

Applies To

11x;12x

Solution/Immediate Workaround

Subsite is the better option because subsite is the part of the main site and all the policies extra will be inherited through the main site where as the New Site Collection site will create a new Sharepoint site and you would need to add all the details manually .

Winshuttle do not recommend stopping inheritance as it might impact other scenarios like workflows.

Please Create subside but do not break inheritance users can simply stop or change the roles ..

Policies do not get inherited.