Microsoft Teams organises work in three containers people mix up. A Team is a membership group (usually a Microsoft 365 group in Entra ID). A channel is a named topic inside that Team, with its own conversation and files. A chat is a thread between people and does not create a Team.
Meetings can start from a channel or from a chat. The recording and the files follow that choice.
Team, channel, chat
A Team has owners and members. Owners add people and change settings. Members post and work in channels. A Team that is “org-wide” or that contains the whole company is a broadcast surface, not a project room.
Channels come in three membership styles:
- Standard: every Team member can see it. Files sit in the Team’s SharePoint library, in a folder for that channel.
- Private: only invited Team members. Files sit in a separate SharePoint site, which is why permissions feel different.
- Shared: people from other Teams (and sometimes other tenants) can be added without joining the whole home Team.
A chat is 1:1 or a small group. Files dropped in a chat land in the sender’s OneDrive and are shared to the participants. When those people leave, the file ownership is still personal. That is why a “project” that lives only in a group chat is fragile.
Choosing a Team, a channel, or a chat
- If membership will last and files must outlive one person, create or reuse a Team
- If the topic is ongoing inside that membership, add a channel
- If the topic is a short thread between a few people, use chat
- Move decisions and records from chat into the channel when they become official
- Add guests at the Team or shared-channel level, not by forwarding a personal chat
Meetings and the rest of Microsoft 365
A channel meeting is visible to the channel and stores artefacts against that Team. A chat meeting is visible to the invitees. Calendar invitations in Outlook can still create a Teams meeting; that meeting is not automatically a channel.
Tabs, Planner, and SharePoint pages can hang off a channel. They do not replace a written library structure. A channel with twenty tabs and no file convention is still a pile.
Guest access is a Team-level and tenant-level setting. Inviting an external person into a chat is not the same as adding them as a guest member of the Team.
What not to do
Do not create a new Team for every small task. You will orphan SharePoint sites. Do not put every department in one Team with fifty channels if those departments should not see each other’s files. Do not use private channels as a substitute for a second Team when the membership is a standing committee that will last years.
Owners should be at least two people. A Team with one owner is a leaver incident.
A practical example
A project runs in a six-person group chat. Files are named “final_v7.” When a contractor is added, someone forwards the chat. The revision creates a Project Team, a standard channel per workstream, stores files in the channel library, and adds the contractor as a guest to that Team only. The old chat is used for quick pings, not for records.
Key takeaways
- Team = membership. Channel = topic plus files. Chat = a thread.
- Channel files are SharePoint. Chat files are OneDrive.
- Two owners per Team. Do not invent a Team for every task.
- Guests belong on the Team or shared channel you intend them to see.
FAQ
Is every Team a Microsoft 365 group?
Standard Teams are. Some configurations exist for special cases. For everyday SME use, creating a Team creates the group, the SharePoint site, and the mailbox/calendar that go with it.
Can we hide a standard channel from some members?
Not cleanly. Use a private channel, a shared channel, or a separate Team. Hiding is not a permission model.
Should announcements go in chat or in a channel?
Use a channel (often named General or Announcements) so late joiners can still read them. Chat is a poor archive.