Microsoft Teams has three privacy settings you can choose from: public, private, or org-wide. Whichever team type you select depends on the information shared within the group. If we’re talking about sensitive and confidential information, it’s best to create a private channel. Not everybody needs access to sensitive information that includes expansion plans, budgets, ongoing competition analysis, and so on.
But there may come a day when you realize you should actually change your channel settings from private to public. Let’s see how you can do that.
How to Change a Channel from Private to Public on Teams
- Navigate to your team’s privacy settings. Click on More options and select Edit team.
- Change the channel’s privacy settings from Private to Public and hit Done. That’s it.
This change also modifies your SharePoint site permissions. In other words, all the people from within the organization can now access your SharePoint files. Of course, external users won’t be able to access your folders.
If you need to undo the changes, you can follow the same steps and change your now public channel back to private.
Private Channel Limitations
Perhaps the most important detail to keep in mind is that you can’t copy private channels to a new team that you create from an existing team. That’s one reason why you may want to change your channel settings from private to public.
There is currently a limit of 30 private channels per team. But this should be more than enough for the average user, as well as medium-sized companies and corporations. In addition to the 30 private channel limit, each team can create up to 200 standard channels.
Microsoft Teams users can easily change their team and channel privacy settings. This means you can change a channel from private to public at any given moment. The same is valid if you want to restrict user access and change your channel from public to private.
Have you experienced any issues after changing your channel’s privacy settings? What happened exactly? Share your thoughts in the comments below.