> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tied.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Notifications
> Three independent channels — audio, email and push — each with its own switches. Tuning them is the difference between noticing what matters and ignoring all of it.
All per person, on your own [profile](/admin/profile). Nothing here affects a colleague, and nothing reaches a customer.
Three separate systems that do not share settings:
| | Reaches you | Best for |
| - | - | - |
| **Audio alerts** | In the dashboard, while it is open | Working a live queue |
| **Email notifications** | Your inbox | Things you must not miss while away from the dashboard |
| **Push notifications** | Browser or mobile | Being on call without watching a screen |
**The default is narrower than people expect: assignment only.** A new member is created with
exactly one email flag and one push flag — the conversation was assigned to you — and nothing
else. So the risk here is the opposite of noise: you can go a long time assuming you are being
told about things nobody has switched on. Turn on only what would change what you do in the
next hour, and check this page rather than assuming.
## Audio alerts
*"Enable audio alerts in dashboard for new messages and conversations."*
### Which conversations
Three independent checkboxes — tick any combination:
| Option | Covers |
| - | - |
| **My assigned conversations** | Conversations assigned to you |
| **Unassigned conversations** | Anything in the queue with no owner |
| **Open conversations assigned to others** | Your colleagues' work |
The app tells you what your combination means as you set it. A few worth knowing:
* Nothing ticked — *"You haven't selected any options, you won't receive any audio alerts."*
* Assigned only — *"You'll receive alerts for conversations assigned to you."*
* Assigned + Unassigned — *"You'll receive alerts for your assigned conversations and any unattended ones."*
* All three — *"You'll receive alerts for all conversations."*
**Assigned + Unassigned is the setting that suits most people.** You hear your own work and you
hear anything nobody has picked up — which is the only other category where a sound should make
you act. **Open conversations assigned to others** is for a team lead watching the floor, and for
almost nobody else.
### Alert tone
**Alert tone:** — the system default, or your own upload. Use a distinct one if you run Tied beside other tools that ping; a sound you cannot attribute is a sound you learn to ignore.
**Play sound** previews it.
### Alert conditions
Two more checkboxes:
| Condition | Effect |
| - | - |
| *"Send audio alerts only if the browser window is not active"* | Silent while you are looking at Tied; audible when you have tabbed away |
| *"Send alerts every 30s until all the assigned conversations are read"* | Repeats until you read them |
The first is almost always right — you do not need a sound for a message you are watching arrive.
The second is deliberately persistent. **Turn it on when a missed conversation is genuinely costly**, and accept that it is designed to be annoying; that is the mechanism. Turn it off if you triage in batches, or it will nag you through work you are already doing.
## Email notifications
*"Update your email notification preferences here."* Each is a separate checkbox:
| Notification | Fires when |
| - | - |
| A new conversation is created | Any new conversation on an inbox you are on |
| A conversation is assigned to me | You get an owner's responsibility |
| You are mentioned in a conversation | A colleague `@`-mentions you in a [private note](/inbox/collaboration) |
| A new message in an assigned conversation | The customer replies to something you own |
| A new message in a participating conversation | The customer replies to a thread you are [participating in](/inbox/collaboration) |
| A conversation misses first response SLA | See [SLA policies](/automation/sla) |
| A conversation misses next response SLA | |
| A conversation misses resolution SLA | |
**A defensible starting point: mentions, assignment, and the three SLA misses. Everything else
off.**
Those five share a property the others do not — each means *somebody is waiting on you
specifically, and the dashboard did not tell you because you were not in it*. "A new conversation
is created" on a busy inbox is a mail rule waiting to happen, and a notification you filter to a
folder is a notification you have already turned off, just less honestly.
## Push notifications
The same event list as email, set independently — so you can have mentions push to your phone while assignment only emails you.
Push needs browser permission the first time you enable it. If nothing arrives, check the site permission before checking anything here; a browser-level block is silent and looks exactly like a broken setting.
**Do not mirror your email list into push.** The two arriving together for the same event is how
people end up muting both. Push is for what needs you *now*; email is for what needs you *today*.
## The inbox notification list
Separate from all three: the in-app **Inbox**, which collects notifications inside Tied.
Whether reading a conversation clears its notifications is set under **Inbox notifications** on [Personalisation](/admin/personalisation#inbox-notifications) — **Clear automatically** or **Keep until dismissed**.
## Next
Theme, layout, and the inbox-notification behaviour.
What the three SLA notifications are measuring.
Mentions and participants — what triggers the rest.
Where these settings live.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.