Private/Public Folders of Department in Communicationpage and Teamsite?

Brass Contributor

Our departments have Private/Public folders on the network drive.

The departments can read/write in both folders, but the public folder is accessible for everybody.

 

If those folders are migrated to SharePoint, I am wondering if we should:

 

- Create a Communicationpage for the public files

- Create a normal Teamsite (without a group) for the private files

- Connect both with a hub 

 

Collaboration will take place in MSTeams where drafts etc. will take place.

 

The files are far below 100.000, so we could also:

 

- Create a single Teamsite with two libraries:

   - Private library

   - Public library (unique permissions, everybody can read)

 

What is better? Where are the pros and cons?
AFAIK I am following the best practice of MS with the first approach. But two sites feed "too much" somehow... 

 

 

1 Reply

Hello @David_Elsner 

 

i vote also for 1.

 

I follow often the inner-outer loop concept (see here for more information: https://www.ioz.ch/blog/was-es-mit-inner-loop-outer-loop-auf-sich-hat-und-worin-sich-teams-und-yamme...

 

- outer loop (information for everyone): Public documents in a communication site or team site not groups connected. It's like an intranet, with informations for all users.

- inner loop (the departments store): Private documentes are stored in a Teams, an his team site connected SharePoint Site. It's the store from the departments. 

 

With this concept every user know, in which case, inner or outer loop, he use which site. Public are for all, private are "my's".

For a better usability, you can add a Teams tap to the public store, or you can create links with target audience for the department users.

 

Hope this helps.

 

Best, Dave