How can we make Microsoft Teams better?

← Public

Ability to archive channels

Would be nice if we had the ability to archive channels. For example: we created a channel for a specific project. Once the project is complete, we can archive that channel or at least move it out of the primary view. I could see the channel list getting large and clunky quickly with multiple projects many of which are complete.

Also, when a conversation in the channel is complete it should be archived or hidden.

17,653 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Cory shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

953 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anonymous commented  ·   ·  Flag as inappropriate

    Please please take this request off the backlog. Archiving a channel is necessary to reduce the number of channels for projects that have been completed. We don't want to delete as we need to keep the history..... or at least allow export of the chat.

  • Kerrie Jarman commented  ·   ·  Flag as inappropriate

    Please relook at this request. We encourage users to create a channel for a project or event but once it is over it just sits there clogging up. For instance there is a short project. We will have a channel for it but we don't want that sitting there forever once the project is finished. It would be very helpful to be able to go back to it when a similar project starts up, so don't want to just delete it. How hard is it to archive a channel so it is not in the main view?

  • Iu Corbe commented  ·   ·  Flag as inappropriate

    Hello, this petition whould be considered with a higher priority. Note also that the ability to archive/export a channel conversation will allow community managers to analyse the threads in search of trending words, create word clouds of all what has been discussed in a channel, quicky identify issues users could be reporting in channels devoted to gather the opinions and experiences of the end users... there are only benefits related to this petition.
    Also, some Teams, as someone said, are run like some kind of project repository, thus, it is easy to reach the limit of channels in the Team; hence, the ability to archive and delete a channel not to block the Team is very necessary.
    Thank you in advance for your interest on this topic

  • e commented  ·   ·  Flag as inappropriate

    please fix this asap!! we are stuck with channels for projects that were completed months ago but we don't feel comfortable deleting all the info. this is extremely important, especially since permissions can be channel-based now. please move this up the priority list! please!

  • RK commented  ·   ·  Flag as inappropriate

    I am new to MS-Teams. It baffles me how this feature request can be sitting in the backlog shelf for 3 yrs and not make the cut to development. I guess that's the difference between a scattered mind and an organized mind (or a corporation vs a start-up, you get the drift). I get the fact that you want everyone to create hundreds of thousands of separate teams for each topic/project but there is also a group of users that like organization...and don't like having to recreate teams every time a new topic/project develops. When you are dealing with a large organization or enterprise, channels makes sense...archiving channels makes even more sense (given the 200 channel limitation versus unlimited). Please review your use case scenarios and sales/user guide documentation. A good example is your reference to an org-wide team. Setting up an org-wide team is a great idea which acts as a shell where nuggets of informational data transpire across separate channels. But what happens when you hit the 200 channel limit? Do you want organizations to archive the team and start over every time they hit the 200 channel limit? Each channel has its own lifecycle, what if you can't archive a team because there are channel(s) that are still actively used? Can we move the active channel to another team so we can archive the old team? Oh wait, that feature is on backlog as well (https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16939708-move-channels-into-other-teams)...go figure. I hope you reconsider your decision and move this feature up your priority list. It's the difference between treating MS-Teams as a toy versus a solution.

  • Brijit Khanna commented  ·   ·  Flag as inappropriate

    Hi,

    This should be already part of the initial setup, after implementation of Teams about a year ago in our organisation this became more of a "need to have" instead of a "nice to have". Please add this. Teams and channels are piling on.

  • Craig Goodall commented  ·   ·  Flag as inappropriate

    We are implementing Teams across our company. I'm really surprised this is not a part of the program already.

  • M commented  ·   ·  Flag as inappropriate

    Any news when this will be move from backlog to a sprint?

  • Elbert Lawrence commented  ·   ·  Flag as inappropriate

    Please do this we have many incidents and projects and need to keep the information for known error database (KEDB), incident model, as well as audit purposes.

  • Anonymous commented  ·   ·  Flag as inappropriate

    For us its super important.
    We often have to create teams to engage with client teams. But also need to revoke access to the working teams at a point. Being able to stop a channel within a group would help this a lot.

1 2 … 5 7 9 … 47 48

Forum Home

Reference Information for Teams

Public: Teams and Channels

Categories

Feedback and Knowledge Base

(thinking…)

More Teams Information