Summary

Microsoft Teams puts three different things behind windows that look almost identical: teams, channels, and chats. Sending a message into the wrong one is how a private comment ends up in front of forty colleagues, and how a file becomes unopenable for the one person who needed it. This guide explains what each one actually is, and gives you a rule for choosing between them.

In this guide

• 1. The Team — a Group of People and Everything That Belongs to Them
• 2. The Channel — a Topic Inside the Team, Visible to the Whole Team
• 3. The Chat — a Private Conversation Owned by the People In It
• 4. Choosing Between Them — One Rule That Settles Most Cases
• 5. Where Your Files Actually Go — the Difference Nobody Is Told
• 6. Posts and Replies — Why Teams Threads Feel Different from Slack
• 7. Standard, Private, and Shared Channels
• 8. Why You Cannot Find That Old Message

Before You Start

• No prerequisites — this is an informational reference guide.

Instructions

1. The Team — a Group of People and Everything That Belongs to Them

A team is a named group of people plus the shared workspace that comes with them.

When someone creates a team, Microsoft 365 quietly creates a set of matching resources behind it: a SharePoint site for the team's files, a shared calendar, a shared notebook, and a group address you can email. You never see most of that machinery. What you see is a name in the Teams list on the left, with channels nested underneath it.

The important part is that membership is managed at the team level. You add a person to the team, not to individual conversations inside it. The moment they join, they can read everything in every standard channel — including conversations that happened months before they arrived.

Teams are for durable groups: a department, a project that will run for months, a committee. Creating one for a two-day conversation leaves an empty room and a SharePoint site nobody maintains. When a group genuinely warrants one, How to Create a New Team in Microsoft Teams walks through the setup; for the plumbing underneath, see Understanding Microsoft 365 Groups, Teams, and SharePoint Sites.

2. The Channel — a Topic Inside the Team, Visible to the Whole Team

A channel is a subject heading inside a team, and this is the concept people get wrong most often.

Every team starts with one channel — General — and gains more as the work splits into topics: Budget, Website Redesign, Hiring. A channel is not a group of people. It is a folder for a conversation, and the people who can see it are everyone in the team.

That is the sentence worth rereading. When you type into a channel, you are not talking to whoever replied last. You are posting on a noticeboard that every member of the team can read, search, and scroll back through indefinitely. This is why the classic Teams mistake happens: the compose box at the bottom of a channel looks identical to the compose box at the bottom of a chat, so a message meant for one colleague — about a salary, a frustration, a person — lands in front of the entire department.

Nothing about the screen warns you. The habit that prevents it is checking the name at the top of the window before you press Enter: a channel shows the team name with the channel name beside it, and a chat shows a person's name.

3. The Chat — a Private Conversation Owned by the People In It

A chat is a conversation between you and one other person, or a handful of people, and it belongs to nobody but the participants.

A chat is not inside a team. It has no owner, no admin, and no SharePoint site. It lives in your Chat list, and it exists for exactly as long as the people in it keep it. Nobody can be added to a team and thereby gain access to your chats — they are outside that structure entirely.

Two behaviours follow from that:

• A one-to-one chat cannot grow. Add a third person to a two-person chat and Teams starts a new group chat rather than expanding the old one, because the original conversation is between those two people.
• History is shared deliberately, not automatically. When you add someone to a group chat, Teams asks how much of the earlier conversation to share with them — none of it, part of it, or all of it. The default is not "everything", which is the opposite of how a channel behaves.

Chats are the right home for a quick question, a private aside, or anything genuinely personal. For what the chat window can actually do — formatting, reactions, pinning, saving — see How to Use Teams Chat Features.

4. Choosing Between Them — One Rule That Settles Most Cases

The decision rule is a question about the future, not the present.

If the answer would be useful to the team next month, it belongs in a channel.

That single test resolves the majority of real cases:

What you are doing	Where it goes	Why
Asking how the expense process works	Channel	The next person to wonder will find your question and its answer.
Telling one colleague you are running ten minutes late	Chat	Nobody needs this in a month.
Sharing a document the team will work from	Channel	It lands in the team's own file store, where everyone already has access.
Discussing someone's performance, pay, or a complaint	Chat	A channel is readable by the whole team, including people who join later.
Announcing a deadline change	Channel	It becomes the record everyone can point back to.
A twenty-message back-and-forth between two people	Chat	Move it out of the channel and post the conclusion there instead.

The pattern behind the rule: a channel turns a conversation into a searchable record for a group, and a chat keeps it disposable and private. Sending everything to chats feels considerate and quietly destroys the record — the answer you gave in a chat helps one person, and the same answer in a channel helps everyone who searches for it later.

5. Where Your Files Actually Go — the Difference Nobody Is Told

A file sent in a chat and a file posted in a channel end up in two completely different places, and this is the source of most "I can't open that" messages.

• A file posted in a channel is stored in the team's SharePoint site, in a folder named after that channel. Every team member can open it because they already have access to the site. Nothing needs to be shared, and the file survives you leaving the company.
• A file sent in a chat is stored in your own OneDrive, in a folder Teams creates for chat files. What actually travels in the message is a sharing link, and that link grants access to the people who were in the chat.

That second point explains a common failure. A colleague forwards your chat message to someone else, that person clicks the file, and the screen asks them to request access. The link was never theirs. The message moved; the permission did not.

The fix is to decide by destination rather than by convenience: if more than the current handful of people will ever need the file, post it in a channel from the start. Understanding Where Your Files Live covers the full picture of what sits where across OneDrive, SharePoint, and Teams.

6. Posts and Replies — Why Teams Threads Feel Different from Slack

In a channel, a message is a post, and responses belong underneath it as replies.

Every new post starts its own thread automatically. There is no separate decision to "reply in a thread" the way there is in Slack — in Teams the thread already exists the moment someone posts, and the only question is whether you put your answer inside it or start a fresh post.

That is where it goes wrong. The prominent compose box at the bottom of a channel starts a new post. The Reply box sits underneath each existing conversation and is visually quieter. Answering in the wrong one splits a question and its answer into two unconnected threads, and six months later the channel reads as a list of unanswered questions.

The habit: to respond to something, use the Reply box attached to that post. Use the main compose box only when you are raising something new.

If you have come from Slack, the mental adjustment is that Teams channels are a list of small conversations rather than one continuous stream — closer to a discussion board than a chat room. Understanding Slack Channels vs. Threads vs. DMs covers the Slack side of the same distinction.

7. Standard, Private, and Shared Channels

Not every channel is visible to the whole team, and the three types differ by who gets in.

• Standard — visible to every member of the team, automatically. This is the default and the one people mean when they say "channel". New team members get the full history.
• Private — a locked room inside the team. Only the team members specifically invited to that channel can see it, and it carries a lock icon in the sidebar. It also gets its own separate file storage, so a document posted in a private channel is not in the main team file store.
• Shared — built for people who are not in the team, including people at other organisations. They get access to that one channel without becoming a member of the team or seeing anything else in it.

The rule of thumb: a private channel narrows access within a team, and a shared channel widens it beyond the team. Both are subject to what your organisation permits. For creating and managing them, see How to Create and Manage Teams Channels.

8. Why You Cannot Find That Old Message

Almost every "the message disappeared" report is a message sitting exactly where it was left, in the other kind of container.

Teams search covers chats and channels together, so the message is usually findable — what fails is the browsing. People retrace their steps through channels for something that was said in a chat, or scroll a chat list for an announcement that was posted in a channel. The two lists are separate, and neither shows the other's contents.

Three things worth knowing when a message will not surface:

• Search by the person, not the phrase. Exact wording is rarely remembered correctly. Who said it usually is.
• Hidden channels still exist. A channel you hid drops out of your sidebar without leaving the team, and its messages remain searchable.
• Leaving changes what you keep. Leave a team and the channel history stays with the team rather than with you. Chat history stays in your chat list regardless of who else leaves.

Troubleshooting

WARNING

A message posted in a standard channel is visible to every member of the team, including people who join months later, and deleting it does not unsend the notification others already received. Before sending anything sensitive, check the name at the top of the window — a channel shows a team name and a channel name, a chat shows a person's name.

Symptom / Error	Potential Cause	Solution
I posted something personal in a channel	Channel compose box mistaken for a chat	Delete the message from your own post (hover the message > More options (⋯) > Delete), then resend it as a chat. Recipients who already saw the notification will still have seen it, so follow up directly with anyone affected.
A colleague gets "request access" for a file I sent	File was sent in a chat, so it lives in your OneDrive behind a link scoped to that chat	Post the file in the relevant channel instead, or reshare it to that person directly.
A new team member says the channel looks empty	They are looking at a hidden channel, or a private channel they were not added to	Ask a team owner to check the channel type. Standard channel history is visible to all members from the beginning.
I cannot find a conversation from last month	It was in a chat, not a channel, or the reverse	Search by the other person's name rather than the wording, and check both the Chat and Teams lists.
My reply started a new conversation	Answer typed into the main compose box instead of the Reply box	Delete the stray post and reply underneath the original one so the question and answer stay together.

Related Articles

• How to Create and Manage Teams Channels
• How to Use Teams Chat Features
• Understanding Microsoft 365 Groups, Teams, and SharePoint Sites
• Understanding Where Your Files Live

Did this solve your problem?