Aug 12 2019 04:07 AM
Aug 12 2019 04:07 AM
When you create a new Teams channel, by default it will deploy a linked team site in SharePoint for the files to be stored in. However, we need to create a Teams channel that links to a communication site, not a team site.
I know you can add an extra tab in Teams and link any document library from any site, but this is not what we want. We need the actual 'files' tab in Teams to be directly linked to a communication site. However, when creating a Teams channel there is no option to choose a comms site, it just defaults to a team site.
Is there any way I can do this?
Aug 12 2019 04:30 AM
I think this is such poor design from Microsoft. We can add the Communications site as an additional document library tab, but it just means any documents uploaded to the Teams channel are stored on some other random team site. We end up with two SharePoint sites linked to one Teams, and one of those sites is just an empty site clogged up with Teams attachments. All it does is creates a mess on our tenant.
Aug 12 2019 04:50 AM
Aug 12 2019 04:53 AM
I can understand that approach. However, we need a department site that's visible to all employees for our department to share information. Since it's such a public site, we want it to be a Communications site. We also want a Teams channel connected to it, since it will let the entire department communicate on it.
Aug 12 2019 04:56 AM
Aug 12 2019 04:58 AM
We'd like to have an IT Communications site, where we can post IT news, updates and documents with the rest of the business.
The teams channel, however, is just for the IT department to communicate internally. Sometimes we have announcements that everyone needs to know about, or just want a quick informal way to send people messages. So the Teams channel wouldn't be public to the rest of the business.
Aug 12 2019 05:04 AM
Aug 12 2019 06:28 AM - edited Aug 12 2019 10:50 AM
@Toby McDaid Are there specific features of a Communications site that you want to use, ones that a Team Site doesn't provide? Or are you just interested in a Communications site because it allows everyone permission to it by default?
If you are only concerned about access and not features, have you thought about granting permissions to the connected Team site by using "old fashioned" SharePoint permissions?
What I mean by this is that instead of adding the non-IT users to the Members group of the IT Team, you would go to the SharePoint site and add them to the SharePoint Visitors group which is found in the Site Permissions -> Advanced Permissions Settings page. This way, your IT Team members will be able use Teams and everything else as members of that group, while other people can be granted access to just the SharePoint team site.
Aug 12 2019 09:36 AM
Aug 13 2019 12:41 AM
To be honest, the only reason we wanted to use a Communication site is to take advantage of the centered page columns. Team sites (in my opinion) don't look great with all the web parts and content pushed to the left of the screen with all that white space on the right hand side. Unfortunately many of our staff have 2K monitors so it can look a bit out of place. We've had many comments in the past saying "why is there all this white space on the right?" and from a user's perspective it looks like we've designed the site poorly.
The full width hero web part is also very useful for our needs too. We can use it to display our IT services in a nice visual banner, better than what the team sites seem to offer as far as visual apps go.
Jan 25 2021 07:38 AM