4 votesMads Nissen shared this idea ·
Hi Everyone – thank you for your patience. As was commented by someone below, Suphatra is no longer at Microsoft, but rest assured we are working on this feature.
I think private channels is a HORRIBLE IDEA. This is why:
1. It allows too-big and defocused teams which creates noise and not signal
2. It inhibits team comms: "I put the document in teams!" - "I can't see it" "no you're not part of the private channel"
3. Fine-grained permissions have been tried over and over and over again and HUMANS DO NOT UNDERSTAND IT. Refer to any file share or legacy sharepoint mega doclib with broken permissions to confirm.
The solution to this lies in structure; so we are much better off investing in channel-move or channel-copy, and also in features that allow for drafting-motions in 1-1chat supported by OneDrive4biz which can be merged into a team when ready for disclosure.
Private channels in a team is an oxymoron - there should not be a "select few" in a team, it simply defeats the purpose.
We are working on this!
The ability for an owner to do "Move Channel" or "Copy channel" would be *incredibly powerful* in a content management perspective. The biggest enemy of Teams adoption is duplication of content, and the defocusing of conversation. Move or Copy channel should provide the option of including chat history, Files and tabs in the transition to a different team. A limitation on visibility (aka only public-public moves) would be ok. An option for "auto invite missing members" would make sense but is not an absolute.
Leaving behind a forward link both in source document library and source team which directs users to the new location of the channel would be magnificent.
Also the conversation in the channel should show the time-posted label with a hover that displays what local time it was posted in. Furthermore, the Appointment scheduler should show options for the participants (most likely) timezone.
This request is now being reviewed by the feature team! I’ll keep you posted as to the future decision.
A feature long missing from Yammer should be architected for Teams: the ability to fusion and fission channels and allow admins to move messages.
In an organic roll-out the sensible channel structure usually emerge organically, and your first hunch is wrong in 99% of cases. However, due to merging and splitting being super difficult people are forced to stay in the imprecise scopes of the original channels, decreasing the signal/noise effect.
Like in the old SigOp days on BBS'es, and in old newsgroups, owners should be able to instructively move messages to other more appropriate channels when a user posts it in an irrelevant place.
User Story:The teams owner selects Message(s) and clicks ellipsis to choose Move To -> *ChannelList* in order to place the message in the relevant channel.
Secondly it should be possible to merge two channels seamlessly including history etc.
Finally it would make sense to be able to select a bunch of messages and do Move To -> New Channel
This feature is still on the backlog.