Forum Discussion
Teams Public Preview Office Hours - Teams Connect Shared Channels
Shared channels is in public preview. We are excited to see the response from our Public preview community and thank you for your great feedback. We are organizing a live Q&A on https://docs.microsof...
Hi, loving this new type of channel, really see it as the new channel standard as it offer a chance to make changes in the channels lifetime as to how public or closed it is.
But I had an issue when establishing a number of them at the same time. Only half of them managed to establish sharepoint area for itself, and trying to establish new ones resulted in the same hang up. The solutions turned out to be changing the channel name, then suddenly it was ok, and then change back (seemed to be necessary as it could not quite forget its old name).
But I had an issue when establishing a number of them at the same time. Only half of them managed to establish sharepoint area for itself, and trying to establish new ones resulted in the same hang up. The solutions turned out to be changing the channel name, then suddenly it was ok, and then change back (seemed to be necessary as it could not quite forget its old name).
I like the shared channels but I don't like how the SharePoint sites are named and the URL's they get. Users should have more control over this!
I don't understand why a new SharePoint site has to be created for every new shared or private channel when you can override permissions per folder in SharePoint? It's really disturbing and poor design as you don't have ONE SharePoint site where you can access all files in the team.
If channel folders with overridden permissions where used, and located in the main SharePoint site, it should be relatively easy to make it possible to convert from public to shared or private channels, or from private or shared to public, but with the current design it's not possible, if it ever will be.
