Module 3 of StartCloud's Microsoft 365: Everyday Skills learning pathway, in five short units with a knowledge check: how to decide between a channel and a chat, why a file shared in a chat lands in your OneDrive while a file posted in a channel lands in the team's SharePoint library, how to set Teams notifications so you can live with them, and how mentions, tags, status and quiet hours keep a team reachable without being exhausting.
Teams Without the Noise
Channel or chat, and how to decide
Teams gives you two places to type and never explains which one to use. So most of us default to chat, because chat feels quicker, and over a couple of years an entire business quietly ends up with its decisions, approvals and files locked inside private conversations nobody else can see.
There is one difference worth remembering, and everything else follows from it. A chat belongs to the people in it. A channel belongs to the work.
A channel belongs to the work
A channel sits inside a team, and everyone in that team can read it. Post there and the conversation stays with the project, not with you. Someone who joins the business in March can scroll back through February and catch up without asking anyone a single question.
- Anything the team would want to find later
- Decisions, updates, questions with an answer worth keeping
- Files the team owns, rather than files you happen to have
- New starters can read it without being invited to anything
A chat belongs to the people in it
Chat is the corridor conversation. It is quick, it is casual, and it is completely invisible to everyone who is not in it. That is genuinely useful for the small stuff, and it is exactly why important things should not live there.
- Quick questions with a short shelf life
- Are you free at two, and did you eat my yoghurt
- Anything genuinely private between a few people
- Nobody can find it later, and that is the trade you are making
Would this be useful to somebody else, later? If yes, it goes in a channel. If you honestly cannot imagine anyone ever needing it again, chat is fine. That is the whole test, and it takes about a second to run.
You know the one. It started with three people and a question, it now has eleven people, a nickname, and six months of decisions in it. Once a group chat is making decisions and holding files, it has become a channel that nobody got around to creating. Move it. Everyone will grumble for a day and thank you for a year.
Standard. Visible to everyone in the team. This is the normal one, and the one you should reach for unless you have a reason not to.
Private. Only the people specifically added to it can see it, even other members of the team. Useful for genuinely sensitive work, and easy to overuse until nobody can find anything.
Shared. Lets you bring in people from outside the team, and in some setups from outside the business, without adding them to everything else.
Here is the thing almost nobody has been told, and it explains a surprising number of missing files. Where a file lands depends entirely on whether you dropped it in a chat or in a channel. Teams does not mention this. It just quietly files it somewhere and moves on.
The file is uploaded to your own OneDrive, and everyone else in the chat is simply given permission to open it. The file is yours. They have a link to it. It sits in your storage, under your account, tied to your name.
The file is uploaded to the team's SharePoint library, into that channel's folder. It belongs to the team from the moment you hit send, and it stays there whoever comes and goes.
Every team in Teams has a SharePoint site sitting behind it, whether anyone has ever looked at it or not. Each standard channel gets its own folder inside that team's document library, which is exactly what the Files tab is showing you. Private channels are the exception: each one gets a whole separate site of its own, which is why files there feel oddly disconnected from the rest of the team.
Drop a file into a channel post and it goes into that channel's main folder. Teams does not stop and ask which folder you meant, so a busy channel ends up with a long flat pile. Nothing is broken, it just needs someone to tidy occasionally. Uploading through the Files tab lets you choose the folder yourself.
Delete a file from the Files tab and it really is gone from SharePoint, but the original post stays exactly where it was. The message only ever held a link, so what is left behind is a link to nothing. Nobody is told. They just click it one Tuesday and get an error.
Because chat files live in the sender's OneDrive, they are tied to that person's account. When someone leaves the business, anything the team relied on from their chats becomes a conversation with IT rather than something you can simply open. Work that matters belongs in a channel.
Nothing technical. Just pause for half a second before you attach something and ask whether the team needs this file or whether one person does. Team file, channel. Personal favour, chat. That one habit keeps years of work out of individual accounts, and you will never notice it working, which is rather the point.
Teams arrives with everything switched on, which is a reasonable guess by a piece of software that has never met you. Left alone, it interrupts you a few hundred times a week, and the usual response is to turn the whole lot off and stop looking. Both extremes are bad. There is a comfortable middle and it takes about ten minutes to set up, once.
The mental model that makes this easy: a banner is an interruption, the activity feed is an inbox. Most things belong in the inbox. Very few things have earned the right to interrupt you.
- Someone @mentions you by name
- Direct chats and calls from actual humans
- The two or three channels your job genuinely depends on
- Anything the business has agreed counts as urgent
- Every reply in every channel you have ever been added to
- Likes, reactions and thumbs up on things you posted
- Channels you were added to once, for a project that ended in 2024
- Your phone buzzing for something you already read on your laptop
Your overall notification settings. Click the three dots next to your profile picture at the top of Teams, then Settings, then Notifications and activity. Everything for the whole app lives here. For each type of thing, you choose whether it shows a banner on screen, only appears in your activity feed, or does nothing at all. Banners are for things you must react to now, which is a much shorter list than the default suggests.
Each channel, set individually. Hover the channel name, click its three dots, then Channel notifications. This is the one hardly anyone touches and easily the most useful. Set the two channels that genuinely matter to notify you on every post, and leave everything else on mentions only.
Hide the channels you do not need. Same three dots on the channel, then Hide. It leaves your list short and honest without leaving the team. Hidden does not mean gone: everything stays searchable, and it reappears the day the project restarts.
Your phone, which is a separate set of settings entirely. Teams on mobile keeps its own notification settings, which is exactly why your laptop can be perfectly civilised while your phone goes off in the car park. Open Teams on your phone, tap your profile picture, then Notifications. Fix both, or you have only done half the job.
The feed only holds the last few weeks. Microsoft keeps notifications there for about thirty days and then they drop off. So treat it as a to-do list you clear, not a filing cabinet you rely on. If something in there matters beyond this month, it needs to be a task, a note, or a file, not a notification you keep meaning to get back to.
Notification settings are only half the story. The other half is how the rest of us write, because your settings cannot save you from forty people who mention everybody for everything. Mentions are the volume knob for the whole team, and there are three of them.
@ someone by name
Typing @ and a person's name marks the message as being for them. It lands in their activity feed with their name on it, so it survives the scroll even if they are heads down all afternoon. This is how you ask a specific person for a specific thing.
- Use it when you need a reply from one particular person
- Do not use it as decoration for a message they were reading anyway
- If nobody is mentioned, treat the post as read it when you get to it
@ the whole team or channel
Teams lets you mention an entire team or channel in one go, which pings every single member. It is genuinely useful about four times a year: the office is closed, the system is down, the fire drill is at two. Used weekly, it is the fastest way to train everyone to ignore you.
- Reserve it for things that are true for everyone, right now
- Ask yourself who would be annoyed to be interrupted by this
- If the honest answer is most of them, it is a normal post
Tags, for a group of people
A tag is a named group, something like Roster or First Aid, that you can @mention exactly like a person. Everyone in the tag gets notified and nobody else does. If your team keeps reaching for the whole-team mention because five people need to know, a tag is the fix, and a team owner can set one up in a couple of minutes.
- Notifies the tagged people, quietly ignores everyone else
- Perfect for a roster, a duty group, or a small subset of a big team
- Ask a team owner if you do not have the option to create them
Status and quiet hours are the other half of the deal. Your status is not a report card and nobody is scoring you on it. It is a courtesy, telling colleagues whether this is a good moment.
Setting yourself to do not disturb for two hours to finish something is a completely normal thing to do, not a small act of rebellion. Teams holds the banners back while it is on. There is also a priority access list, so a short list of people can still get through when it genuinely matters. Set it up once and stop feeling bad about focus time.
Teams on mobile can be told which hours and which days it is allowed to make noise, so it stops buzzing at ten at night and on Sundays. It is one of the best five minutes you will ever spend in a settings screen. Some businesses set this centrally for everyone, so if the option looks locked, that is why.
Half a line, something like on site until 2, replies will be slow, saves a dozen people wondering and three of them following up. It appears next to your name and when someone starts typing to you, which is exactly where it is needed.
This is the part worth taking seriously. If a channel is so noisy that every member has quietly muted it, it has stopped being a way to reach people. It looks like a working team from the outside and functions like a wall. The fix is never louder notifications. It is fewer and better posts: mention the person you need, keep replies in the thread they belong to, and let the whole-team mention go back to being rare. Muting is a symptom. The posting habits are the illness.
- Microsoft Learn: Overview of Teams and SharePoint integration
- Microsoft Learn: Intro to file collaboration in Microsoft 365, powered by SharePoint
- Microsoft Learn: Overview of standard channels in Microsoft Teams
- Microsoft Learn: Private channels in Microsoft Teams
- Microsoft Learn: Manage tags in Microsoft Teams
- Microsoft Learn: Quiet time policies for iOS/iPadOS and Android apps
All of this was current at the time of writing (August 2026). Teams changes its menus and wording more often than most apps, so if a button is not quite where we describe, the setting almost certainly still exists under a slightly different name nearby. The links above are the freshest word on how it works underneath.
Knowledge check
5 quick questions. Get 4 right and the module is yours.
1. You attach a spreadsheet to a Teams chat with two colleagues. Where does that file actually get stored?
2. You tidy up and delete an old file from a channel's Files tab. What happens to the message it was posted in?
3. Your team has agreed a new process, and it is the sort of thing new starters will need to know. Where does that go?
4. Four people in your thirty-eight person team are on the roster this week and need to see a change. What is the best way to notify them?
5. You discover that every single member of a busy channel has muted it. What does that actually tell you?