Support for Private Channels
Looking for the ability to create a channel that only channel members can see. Private channels are available in slack. There is an admin for private channels who is the creator, and they are the ones who add/remove users.
Five types of public/privacy that is being asked for by users:
- Public-Open (visible anywhere including outside the org and anyone can join)
- Public-Invitation (visible anywhere including outside the org, must be invited)
- Company-Open (only visible inside the org and anyone in the org can join; outside the org must be invited)
- Company-Invitation (only visible inside the org, must be invited)
- Secret (invisible to everyone except existing members, must be invited)
Angela Sze
shared this idea
We acknowledge the customer demand for Private Channels and have been hard at work on it. Private Channels is currently in preview with a select group of customers. We expect to release the feature to the public later this Fall, and will update here when we are starting to roll out to all customers. We appreciate all the feedback you have provided to us on this forum and thank you for your patience.
~Alex
1885 comments
-
Anonymous
commented
C'mon guys, if you need help, i'll help you. In one day it's done :-)
-
Anonymous
commented
When will this be rolled out? On it's way it's too general... One date please :-)
-
Beau P
commented
I noticed now you can make "Teams" public or private, but you can't make "Channels" public or private. Is this supposed to be this way or is public/private channels still on its way?
-
Haley Engle
commented
Within a team be able to edit permissions to each channel for the team members that channel apply to.
-
Mike baker
commented
is there a roadmap up on this available?
-
Beau P
commented
This is literally the one feature holding our company back!
-
Giulio Vannini
commented
Actually enabling chats with end-to-end encryption using RMS digital rights would give TEAMS a very strong competitive advantage for positioning on confidential executive chats.
Chats that nobody can read other than the addressses would be a powerful compliance feature -
jeffwllms
commented
Really hope this come. Having a bunch of teams with just a general channel is annoying. Setting this up now the way we want it knowing this is in the works. So far we actually have found it isn't so important for teams to not be able to see the project groups they are not specifically on. We actually just received benefit from the fact someone who wasn't assigned to a project checked the channel out and was able to help.
We still need it for the board groups. Because some board committee are private from the entire board. (Governing committee for example). But actually finding this feature is less important than we originally thought.
-
Eduardo Spitzner
commented
Great News!
Microsoft Teams will become a viable option for our needs. -
Anonymous
commented
We like our development team to have access to the Architecture Group but we will like to have a private channel for sharing draft documents between architects.
-
Nick Milner
commented
I have a services team who works on multiple projects so I'd like a channel per project plus a couple of general channels. I don't want every team member in every channel because there could be sensitive material shared, and I'd also like the ability to add customers to their project channels. Right now I have many teams with one channel in each which makes the concept of channels redundant. Thanks.
-
Jaap
commented
This is especially needed when externals work on our projects. We created a team for every customer, and a channel per project with that customer. I don't want another external digging in another project, even though it is within the same customer.
-
Eduardo Spitzner
commented
It already exists a suggestion of this. I understand that is better vote in the same suggestion than crate a lot of paralels suggestions.
-
Anonymous
commented
Add ability to create a new channel within a team but make it confidential between specific team members.
-
Wolfgang
commented
any update on the release of this feature?
-
Matt Coyle
commented
This is very much a needed feature. Otherwise we are going to have to create a different Team for each group. We will be creating several Teams when all we need is one.
-
jeffwllms
commented
I think I have a somewhat different idea. Just do away with the team/channel thing all together. Have groups map directly to channel. You then have a 1 to 1 relationship with group data (another big issue) and you are able to add channels with specific groups. You reduce ui clutter since you don't have the concept of teams and channels.
This also maps more closely to what you see in slack and other system. I think you were trying to create additional functionality by offering the additional level, but it jest seem like it is the root to all the extra confusion and complexity.
-
Stephane Moulec
commented
Totally agree that this is needed. It is nice to centralize a team activity in one group but not everyone needs access to all channels (project, topic, whatever concept a channel represents in an organization). Creating multiple teams as a workaround dilutes info IMHO
-
Alessandro Caviglione
commented
+1
-
c b
commented
This is somewhat related, but I think it would be less cumbersome if the Chat and Teams buttons/areas were combined. So that private chats, just like the planned private channels, are right there along with the public channels. So they are all folder-like, or section dividers in the entire area where you would.. chat. And having the clickable folders to expand of the Teams sometimes gets in the way I think.. until there are a lot of channels where the screen would get cluttered, they all should just show up. The fact that they default as "hidden" until the user selects them as a Favorite is hard to show and explain to new users in our company.