Oct 22 2019 06:27 AM
Oct 22 2019 06:27 AM
For some reason Teams keeps creating a folder called General for a all teams I'm a member of. This is really annoying as it gets replicated on a sharepoint site where we don't want a folder call General. If the folder is deleted it reappears (is created by me) when I log into teams. How can I stop this from happening?
Oct 22 2019 06:30 AM - edited Oct 22 2019 06:31 AMSolution
Hi @AI_birder ,
Afraid there is nothing we can do about that. By default a folder is created in the Standard "Documents" library in the SharePoint site for each channel.
For formal document management I don't use the "Documents" library I create other document libraries to save it getting clogged up with any document or image that gets attached to a Team chat.
Hope that helps
Nov 06 2019 08:25 AM
@Juan Carlos González Martínis there a way to untie the Teams & SharePoint connection? I don't want to have the site connected to Teams anymore and I don't want this random General folder in our documents directory.
The last time I tried removing the Teams connection I ended up deleting the entire SharePoint site. Can you provide guidance?
Nov 06 2019 08:42 AM
@ChemicalEngineer the supported way would be to remove the Team which removes the associated SharePoint site. Then re-create a SharePoint site from SharePoint Home (if enabled by your admin)
Every time you create a Team it creates an Office 365 Group which in turn spins up a SharePoint site collection. This is all by design.
Feb 10 2021 10:49 AM
This is accurate information (General is created) but it's so 'wrong' in every way - who ever wants a folder called 'General'? Surely this is wrong on every level! Microsoft policy is mindblowingly incomprehensible on this sort of thing. Do you use 'General' folders?
May 07 2021 10:10 AM - edited May 07 2021 10:29 AM
Agreed. @timmyd27 This forced creation of a "General" folder inside the SP folder that is the documents for the Team is not a good idea. It seems to be a misunderstanding of the many ways you create Teams.
Sep 23 2021 05:50 AM
Sep 24 2021 08:52 AM
@Gau You can avoid this by creating multiple "libraries"rather than folders inside a library. i.e. a library called HR that is then able to be linked directly to the top level of files in an HR Teams site. It's a mess, I know, cause you can't delete General which is in a totally different location. Need to hammer on MSFT at Ignite about this POS design. Come on MSFT, I know your Dev teams are hearing about this from the corporate 1000 IT people. Fix this please. We need to create a Team from a Library and have the folders inside the library synced to Teams automatically. It can't be that hard. Or am I missing some undocumented feature in SharePoint or Teams Powershell commands (another problematic tool that is not well documented).
Nov 18 2021 09:56 AM
Nov 18 2021 02:55 PM - edited Nov 18 2021 04:19 PM
As I have tried, once you create the new Document library (i.e. HR INTERNAL) you then go into Teams and link it there. I have done this and it did work. The General folder in this example is still linked to a master Document library, but it doesn't need to be. Add a Tab at the Top for the new Library (REVIEWS) by choosing the SHAREPOINT app. It's shown in the images attached. Your users then open the library they need. This makes more sense actually from a security perspective, though the whole design of this is a mess. There should be a clear pointer in Teams to the top level FOLDER or LIBRARY, either one. But I'm sure there was some functional issue that forced the Teams product group to do it this way. I'll do a second way of doing this by creating the Team inside the proper Library to begin with and show that to you as well.