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.
nice, thanks for the update :).
P.S. Thanks for listening that private channels are different then creating whole private teams, although I think it can work that way too. But honestly, I think people should just utilize the group chat feature for private matters since I mean it's Technically, kind of a private channel and works similar, just can't use the bots and all that in chat.
Or you could get educated on how Microsoft security works and realize it's not an easy fix and not spaghetti code. The difference between this and other stand alone platforms they actually integrate with everything and allt he DLP etc. that other solutions don't have, so yeah it's not that easy. If you step back and look how it works with AD permissions etc. at the group level to give permissions to Teams, but they really dont' have a way for channels. I mean, if they store it at the exchange level which I'm guessing they would have to implement some kind of individual permission changes at the folder level just like someone would right click a folder to assign permissions. Probably not an impossible task, but definatley going to be far harder than you give it credit for because it's build on Exchange / AD, not some stand alone security like other similar apps. So it's a blessing because of all the integration and users etc. but a curse at the same time because it makes things harder to create / change.
Go check out Discord and copy them, if you do, your will have gold for business org's on your hand. It has permissions per channel and roles and does things nicely. Not to mention "Voice channels" as well which are nice. The notification system is sweet as well.
But yeah to mirror the other people in these comments, channels are way better than entire Groups/Teams for everything.
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
Honestly, last thread that came in should be where you reply / cursor ends up by default, and if you start a new convo, your cursor shoudl jump into the thread you just posted. And last but not least, Add a New Convo button, and just do away with the text bar on the bottom unless that button is clicked. Then reply's have the bar come inline like it does now, just remove the text box at the bottom unless a new conversation/thread button is clicked.
This request has been reviewed and declined by the feature team.
You can continue to up vote this topic as well as leave comments. Depending on the ongoing feedback, there is always a chance a topic will be revisited based on user demand.
Private channels and shared channels are being worked on. This will satisfy this request since you can either A. Have a Team then have channels for each sub team to access via private channel. Or have two teams each that have a general project shared channel in their team.
This request has been declined by the feature team.
Private channels may help with items such as this request once they are released. The Private channel topic is tracked at http://microsoftteams.uservoice.com/forums/555103/suggestions/16911079
Please note the handling of “Guest Accounts” is a separate ask and can be found at: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16911109-guest-access
The request about “Guest Access at the Channel” level is being tracked by this request: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31374577-guest-access-should-be-implemented-at-the-channel
Thank you all for the feedback.
Most of this request is split about private channels and shared channels. Both are being worked on per principal PM of teams from Ignite session this week.
This is still being worked upon. I hope to have more details in the next couple months.
Please know the team is actively working on this feature.
Check out planner sessions from ignite. They are adding integrations from planner to todo and roughly Outlook tasks.
yes, a mute option would be epic. Or ignore conversation maybe, just like facebook or something, if a thread is going where you can click the top original post and ignore replies.
Per channel settings would be very nice as others have stated. Never can have too much customizations :p. Just give us all the same options we have on the notifications tab but for every channel and add mute and bam, much better!
Yes, definatley need either existing notification settings to be added at the channel level instead of the app level across all Teams. Leave the existing settings as is for default settings but let someone pick how they get notifications for each specific channel.
This request is still being considered by the feature team but a final decision has not yet been made. I’m still awaiting more details.
I disagree, I prefer the Threaded view after using it awhile and getting use to it. I would like the option on per channel basis thou if possible, cause some things are running conversations only, use case "Server Updates" Or perhaps. What may be a better fix is provide a Drill down into a conversation so you can just treat it like a chat on a screen. This might work out actually.
Oh god, please make this happen. The threading just adds confusion and a mess. Discord works great and it's not threaded. Constantly have people not click in reply for a thread and now you have 2 threads, and it is just not a very good user experience. If it's possible to make it optional that would be great, or just disable it all together for the whole team. either way.
Hi everyone — here’s some clarity on our legal compliance.
As of now, Chat history for a Team is stored infinitely and available for eDiscovery/Content Search. So, the answer to your question depends on what you mean by closing the project. If you close the project, but don’t kill the Office 365 Group/Team associated with, everything should be still searchable. You should be able to recall/search for all chat activity that happened within the Team by scoping your compliance content search to the appropriate group mailboxes. The data is not lost.
Please let me know if you have any other questions! You can post a message here or tweet me @skprufo.
No she means leave the team or if you have preservation on your mailboxes you can delete them. Then search via compliance center just like you do a mailbox to retrieve info.
They already journal your chat messages to your mailbox. Just guess they don’t expose it to the users. Please turn that on! Cause right now it looks like chat is limited to 30 day history in the app.
I think this is an iOS limitation. Pretty sure Facebook and other apps do the same thing.
You can get to tabs in the mobile app. It’s in top right corner. Not sure if this has been added since this post but it’s there.
Hi folks, is this still happening for you? If so, please send me your logs at sparavi (at) Microsoft (dot) com. I’ll see if we can repro the issue and figure out what’s going on.
Maybe your admins restrict group creation and thus breaks the create team button.
This feature is still being reviewed by the feature team. No decision has been made yet. I’ll keep you posted.
Yeah leave them separate, however, give us an option in the client to PoP out our chats. If you add this single feature, Skype for Business is history :P.
This feature request is working its way through the backlog queue. No new details are available yet.
Hey guys, I read they are adding support for flow and if this gets added you can easily link a conversation action into a SharePoint list/item on any page you want.
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
Due to a priority shift this request has slipped to the backlog. I hate to bring bad news. I will continue to provide the feature team your feedback and votes.
Hopefully this will move back up in the queue soon.
This request is still on the backlog.