Nov 14 2019 12:45 PM
Nov 14 2019 12:45 PM
I can see the option to create a private channel but I don't see a way to convert/set an existing standard channel into a private channel.
Is this not possible?
Nov 14 2019 01:15 PMSolution
Jan 16 2020 11:19 PM
This will be important feature because channel usage may change. I hope this will be added to Teams in near future.
Apr 09 2020 05:24 AM
Apr 16 2020 01:01 PM
i find this very annoying now that i added new members to team but dont want them to have access to all channels
when is the fix coming
Apr 16 2020 01:17 PM
The way to get your feedback to the product group is through uservoice, as it allows them to balance and prioritise the next developments. Try to give as much detail as possible as it helps them understand the business value.
Jun 30 2020 04:37 PM
@costa2020 There will never be a "fix" for this. nothing is broken. Teams stores all your files in a SharePoint doc library created for that team. Normally all channels will have it's own folder in the Team SP doc library. But with private channels the files must have different permissions. So to accomplish this a different site collection is created for the private channel providing it with it's own SP doc library with it's own set of permissions.
Jul 15 2020 01:46 PM - edited Jul 15 2020 01:47 PM
@Jamie Swindall, we could care less about the semantics of 'broken' and 'fix' or the technicalities of WHERE the files are stored.
The fact of the matter is that a functionality is missing, and not having it results in a very poor product experience.
This feature must be supported and we will vote to help ensure it is.
Aug 24 2020 09:50 AM
@AB321 I agree - we need this feature added as Teams and processes change, so we need to be able to take a channel private if the use case for the team/channel changes.
Sep 16 2020 08:13 AM
I also would like to express that this feature to be able to edit a channel from public to private would be very important. I have also had some frustration from not being able to edit this. At the very least perhaps you include some messaging when setting up a channel that this is an irreversible selection. Adjusting this feature as soon as possible would be much appreciated. Thank you @Goforit5
Sep 17 2020 11:59 AM
@Jamie Swindall I'm always amazed when a software company justifies a bad user experience by explaining the underlying limitations of their design which they did not properly address. Nobody cares about the poor design choices made on the backend. What people do care about is a user experience that actually works. I, like many, have been anxiously awaiting private teams since it was a gaping hole in product, as even Microsoft would finally admit. Now we discover that, well, it's pretty much useless, because it requires you to manually replace every single Team/Channel/Sharepoint in order to achieve anything useful ... if you want to use it, you're pretty much starting from scratch.
How exactly did MS envision existing customers migrate to private channels ? ... sorry, silly to assume the question was actually asked and discussed.
Instead of justifying short-sighted design choices, MS needs to come up with a plan for how they can allow existing Teams/Channels to be seamlessly (i.e., automatically, not manual content forklifts) converted to private such that new private or public channels can be added.
Took years to deliver, and still useless. Wishing we would have just stuck with Slack.
Oct 12 2020 10:33 AM
@ChristianRoy I add my voice to the others that we need the ability to convert channels once they are created.
Oct 20 2020 08:18 AM
Especially when you lose the name of the channel when it's deleted. Converting to private should be easy and simple. Just drop the messages from public and limit members from previous posts.
Dec 09 2020 11:56 AM
This worked for us:
View the MS Team in SharePoint.
In advanced sharing properties click "Stop Inheriting Permissions" on the parent folder of the desired Team. Delete all listed users then re-add users you want directly. Global administrators cannot be excluded and will show as "yourdomain" Owners.
Dec 10 2020 08:38 AM
@JoeMayers SharePoint permissions feature is always there as MS Teams is just a wrapper on SharePoint sites but with chat and other app integration.
If we are able to convert the channel from public to private and vice versa would be handy for any teams user, otherwise we will have to find alternates like this.
When SharePoint does the magic, it will be easy for Microsoft to add such feature on Teams directly as Microsoft is promoting Teams heavily as the way to go application within the enterprises.
Jan 28 2021 02:57 AM
Is there any conclusion or roadmap yet?
Deleting a whole channel with all it's conversations seems to be a really odd way of doing this, I am in the situation right now that I need to add some users to a team that take part in decision making, but they should not see the whole development process of the IT Team in a subchannel that initially was not private.
Mar 05 2021 01:50 PM
Would also like to add my frustration about this. My channels are named after clients, and I've tried to delete the channel and set it up as private, only to have the name 'taken', because the channel does not 'actually' get deleted! Not sure why it is called 'delete'..... The client only has one registered company name, and all my clients are in exactly the same format. So the only way to get around this is to name it slightly differently. Would be much easier to either switch private/public, or just to be able to delete properly and recreate again correctly.
Mar 10 2021 09:03 AM
we're in the exact situation as you. We deleted a public channel and hoping to recreate the same channel name but private. Teams would not let us, saying name is already taken. And we have no way to purged the now deleted public channel.
Mar 19 2021 10:06 AM
How exactly did you do this? I have looked into the teams site in sharepoint but I don't see where 'advanced sharing properties' are. I Sorry I am just trying to follow here and not an MD365 admin person.