The Notifications tab of your profile. This is the setting that most determines whether the platform feels helpful or noisy, and it is worth ten minutes rather than the thirty seconds most people give it.
Delivery channels
Three ways a notification can reach you.
In-app, the bell in the top bar.
Email.
Slack, where your organisation has connected it.
Each can be turned on or off independently, and the sensible arrangement for most people is in-app on, email for the things that genuinely need to leave the product, and Slack only if your team actually lives there.
Email everything is the common mistake. A person who forwards every notification to email has built a second inbox that competes with their first one, and the reliable outcome is that both get skimmed.
Quiet hours
A window during which notifications do not interrupt you, with a start and an end.
Worth switching on. The argument for it is not work-life balance in the abstract: it is that a notification at eleven at night is one you cannot act on and will have forgotten by morning, so it costs you the interruption and delivers nothing.
Notifications raised during quiet hours are not lost. They are waiting when the window ends.
Live activity in the search bar
A quiet line inside the top-bar search box showing what is imminent: your next meeting, a due task, a reminder.
Four settings: off, fifteen minutes, thirty, or sixty.
This is the lead time, and it decides how far ahead something has to be before it earns the line. The bar is silent by default and shows nothing at all when nothing qualifies, rather than telling you that nothing is happening.
Fifteen is right for most people. Thirty suits anybody who needs to prepare for meetings or move between buildings. Sixty turns it into a general awareness of the next hour, which some people like and most find noisy. Off removes the line without removing anything from Home.
Chat is separate, and that is deliberate
The single biggest source of notification volume in most organisations is chat, and none of it is configured here.
Per-room settings live in the room header: all messages, mentions only, or muted. That separation is intentional. How loudly one room pings you is a decision about that room, and burying it in a global settings screen would mean nobody ever changes it.
If your notification volume feels wrong, look there first. Setting busy channels to mentions-only usually fixes more than anything on this tab.
Sounds
A choice of sound styles for notifications, with a preview so you can hear one before committing.
Silence is a legitimate answer and the right one in an open office.
What is not here
What generates a notification. Which events produce one is decided by your organisation's notification policy, not by you. This tab decides how they reach you, not whether they exist.
If you are getting notifications about something that genuinely does not concern you, that is a policy conversation with an administrator, and it is a better fix than muting a channel.
Chat notifications. Per-room settings live in the chat itself, in the room header, because how loudly one room pings you is a per-room decision rather than a global one.
The wellness nudges. The break and lunch prompts on Home follow their own thresholds and are dismissible in place.
Nothing here is permanent
Every setting on this tab takes effect immediately and can be changed back just as fast.
That is worth saying because notification settings are the ones people leave alone out of a vague worry about missing something important. The realistic risk runs the other way: a person who has never adjusted these is being interrupted by things that do not concern them, and is learning to ignore the ones that do.
Turn something off for a week. If you missed nothing, it stays off.
A configuration that works
In-app on, always. It is the one that does not follow you home.
Email for approvals and anything with a deadline, off for everything else.
Quiet hours on, matching your actual evening rather than an aspirational one.
Live activity at fifteen minutes.
Sound off if you share a room, on if you do not and you miss things.
That takes about four minutes and it is the difference between a product that tells you what matters and one you learn to ignore.
Why the volume matters more than it looks
A notification system has exactly one failure mode, and it is not missing things. It is being ignored.
The moment somebody learns that most of what arrives does not concern them, they stop reading any of it, including the one that did. That state is invisible from the outside: the notifications are being delivered, the badge is being cleared, and nothing is being read.
Every setting on this tab exists to keep that from happening. Turning things off is not neglect, it is maintenance.
Where each kind of thing belongs
A rough allocation that works for most people.
Approvals and deadlines deserve email as well as in-app, because they block other people and you may not be in the product.
Mentions deserve in-app, and email only if you are frequently away from the platform.
Feed activity, reactions and digests deserve in-app alone. None of it is time-critical and all of it accumulates.
Anything a system generates about your own work can usually be in-app only, because you will be here.
The test to apply later
After a fortnight, ask one question: when the bell shows a number, do you look at it immediately or does your eye slide past it?
Sliding past means the volume is wrong. The fix is almost never to check more diligently; it is to turn something off until the badge means something again.
Did this answer your question?
No, ask a person