Make it possible to remove and/or rename the default tabs (files & notes)
It would be really great if we would be able to remove / rename the default tabs. A lot of times files / notes are too generic names for the tabs, so renaming would be really helpful then. :-)
I hate to be the bearer of bad news, but this feature request has been declined.
J Blum commented
Can we at least move the tabs to other than the 1st two positions? - I never use them
David Pitts commented
Any Explanation or justification for why this was declined?
During team setup ask for a SharePoint site to use for files and other required teams back sharepoint repositories, then prompt for the files tab document library name.
Provide a migration interface to move existing teams-required lists/libraries to another sharepoint site
Fabián Pertúz commented
Please implement this option, confuses users when they will load the content.
This is never going to happen, unfortunately.
Please, provide a status!
Yes, please let us remove the FILES tab.
When you add a file to FILES, it creates a folder in the SharePoint documents named "General" Why? That is confusing...
Ian Driessen commented
I agree, i want this feature really badly
Kirk T commented
We also want to be able to disable/remove the "Files" tab as it causing users to save files to multiple locations. We could "block" the permission in the SharePoint location but that doesn't disable the tab and confuses users.
Remco Spierings commented
We would also like to disable or remove the files tab for the teams because it creates files in random new sites and we would like to restrict this to to the designated sharepoint location.
The leftmost "Files" tab simply creates confusion for new users - do they look there or look in the channel for relevant files? Bad setup - would like the option to remove it, and frankly "Chat" - why can't that be done in the channels or in Skype? I can put up with "Meetings" because I know that's my calendar.
What is the current status on this topic? The constraint not being able to clearly mark the Teams-Sharepoint as not the one to be used (or just remove the link, not the sparepoint itself) is the reason not to switch to Teams; even though we have positive feedback from the peer group.
We are planning to deploy Teams alongside Sharepoint, and in order to avoid confusing the channel's back-end Sharepoint with our existing Sharepoint environment, we'll need to remove the "Files" tab, or rename and remap where it points to.
I understand the dev team wanting a repository for files that don't live anywhere else except the channel, and to make that place easily accessible for users of all skill levels. However, this setup severely impedes user-friendliness. Simply moving "Files" to a sub-menu so that it's not immediately present in the tabs would work.
Now that we got the "Files" entry on the leftmost (dark) panel, we need to option to REMOVE the "Files" tab, for every channel!
It just takes up space much needed for other tabs...
I need this so badly...
Brandon Blake commented
Wow, all this time and nothing on this issue? Are they not listening?
Please, I'll do anything, just give me the ability to remove the "Files" tab. I've already created and used for years a SharePoint document library that I'll use for the teams.
Yes, would be a good idea, especially to remove the FIles tab. Or give the option to link to an existing Sharepoint repository.
Even being able to move the tab to the right of custom tabs, such as a sharepoint library tab, would be an improvement
See below for one use case for being able to remove the default Files tab, which I suspect others are facing as well, along with a work-around for users until Microsoft implements this.
* I don't want our users to save their files in lots of different SharePoint sites, which makes it harder to find things. I want them to save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)
* We have already created and used for years an awesome SharePoint document library with a taxonomy managed metadata and views everyone loves
* Therefore, in Teams, I want users to only be able to upload files to our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)
Here are the problems I faced that Microsoft could fix, and the workarounds I did to get it to (kind of) work the way I wanted it to -- you're welcome, Microsoft Team users :)
Problem 1: When I add our existing SharePoint document library in a tab, it does not include the fields and metadata I need.
Workaround 1: Create a new tab not as a SharePoint site, but instead add it as an ordinary website, and put in the URL of your document library. (The UI is not ideal, since there is a left hand nav bar in teams I have to do more scrolling to the right to see all of the SharePoint Document Library view, but at least we can access our views and metadata.)
Problem 2a: I can't hide the default File tab. This means that, instead of going to the new tab I created above to get to our existing SharePoint site, some users will see the files tab and upload file to it, leaving a mess ("wait, did I add the file to my new Team file area or to my existing SharePoint document library?")
Problem 2b: I can't change it so that, when you click on the default Microsoft Teams File tab and upload a file, it actually gets saved in our existing SharePoint Document Library instead of the automatically created new Microsoft Team site.
Workaround 2: In the Team File area, I add a link that goes to the URL of my existing SharePoint document library. I name the link "Use this link to the place to save files." I think click on the top nav bar item Open in SharePoint, and from there I clicked on Site Permissions, and set Site Members' permissions to Read-Only.
Result: Users save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically when I created the team, and users have full access to the taxonomy, metadata and views they already know and love from their existing SharePoint site.