05-20-2019 05:23 AM
05-20-2019 05:23 AM
I run a SharePoint team site that its main purpose is maintaining the team's main document library, and last week I added the SharePoint team site to Teams.
My problem is that every channel that is added to the team automatically opens a new folder in the SharePoint library that I built and maintain. I can't move this folder or even designate new channels to a different SharePoint library on the same site to avoid this mess. There's seems to be a major lack of control in the Teams app which is causing the opposite of what it’s meant to do.
If anyone knows differently, please share!
05-20-2019 05:35 AM
05-20-2019 06:04 AM
I get what you say about the "mess" thing but it's mostly meant that the "Teams" library will be used from a Teams perspective, thereby the structure per channel in Teams! Easy and not complicated for users!
If you want to work with files from SharePoint itself, I'd suggest creating another library to avoid this "problem" You can then use the SharePoint tab! If you will use both this and the files tab depends solely on your organisation , setup and needs..
10-14-2019 03:50 PM
Just adding in here, this USED to be how it worked (and quite handy to keep up with modified folders). However, it must be a recent change that Teams is no longer letting you play fast and loose here. Renaming a folder underneath a channel will no longer 'stick'. And you now DEFINITELY can NOT create a channel to an existing folder name as it triggers an error.
I'm midway through a migration and just finding this out now; going to require some fancy legwork to get it working now :\
01-27-2020 10:15 AM
This is definitly a MUST HAVE for Teams... creating channel folders by default in team site in the ROOT of spoint library is a MESS as we grow the number of channels, for instance we create channels monthly to collaborate in monthly reports but the documents we want MUST be stored in another centralized folder with subfolders for each month, and the only ways are: 1) in the end to manually MOVE all files and folders created to there every time or 2) have Teams opened in one EDGE tab (for otehr tasks like forms etc) and the sharepoint folder with the docs opened in another EDGE tab :\
btw adding as a new tab in Teams works only for LIBRARIES, not to specific folders, this is another mess since we'd want only a particular folder deep inside a library and adding the library requires to navigate through it in the Teams tab much likje would do in sharepoint
There should have a menu in Team channel to move file/folder contents to another folder we'd want to, with a 'no override' option, then we'd be able to change the work folder for the channel to wherever and just go back to sharepoint and delete the default folder Team creates with the channel
08-30-2020 01:10 PM
The best way to create a channel from a SharePoint folder is:
Now if you do not want the channel name to be the SharePoint folder name, you will need to edit the Channel and change the Channel name. If you do this after you have verified the files and subfolders desired are all listed in "Files" tab of the channel, they will still exist after a channel name edit. The channel name edit does not change the SharePoint folder name after creation.
Alternatively, you can create the Channel, refresh the Team SharePoint site to find a new folder with the name of the Channel you just created, then move/copy all the files and subfolders from the desired folder into new Channel folder.
09-06-2020 07:19 PM
@ShaneHutchison it would be excellent product development if Teams could let the user choose a default Sharepoint folder to use for each additional channel. Organisations could simply have a TEAMs folder in sharepoint that's sole purpose was holding the docs embedded in Team discussions.
09-07-2020 08:48 AMSolution
This issue with using another site is permissions, by having the default content storage location for files dropped into chat be in the associated site all the Team members are guaranteed permissions. I consider i working documents, and then get my users to publish the files to permanent filing and storage when they are final.