> ## Documentation Index
> Fetch the complete documentation index at: https://docs.joinsayless.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Notifications

> Review your Sayless notifications, see how alerts connect back to conversations and tickets, and adjust which activity surfaces in your inbox.

Notifications help you keep track of work that needs attention. In Sayless, notifications are closely tied to conversations, tickets, assignments, mentions, and connected communication channels.

## Overview

Use notifications to stay aware of work you own or participate in. The most important notification context usually comes from assignment changes, replies, mentions, ticket comments, and subscription-style activity.

The current app emphasizes ownership and participation over a large notification preference matrix. Keep assignments, subscriptions, and mentions accurate so notifications stay relevant.

Start from [Settings > Preferences](https://joinsayless.com/\{workspace}/settings/preferences), [Settings > Connected Accounts](https://joinsayless.com/\{workspace}/settings/connected-accounts), and the work item you want to follow.

| Signal                       | Where it comes from                     | Best practice                                          |
| ---------------------------- | --------------------------------------- | ------------------------------------------------------ |
| Assignment                   | Conversations and tickets               | Assign only the person responsible for the next step.  |
| Mention                      | Comments, notes, rich text              | Use when a teammate needs to respond or review.        |
| Subscription/shared activity | Conversations and tickets               | Follow work when you need awareness but do not own it. |
| Channel activity             | Email, WhatsApp, Telegram, Slack, Teams | Keep channel mappings and accounts connected.          |

## Notification context

Notifications are most useful when they point to a specific piece of work.

### Conversations

Conversation notifications may relate to new replies, assignment changes, subscriptions, or activity in a thread you are responsible for.

Conversation detail headers show active users and subscribers where available, helping you understand who is already looking at or following a thread.

### Tickets

Ticket notifications may relate to comments, assignment changes, property updates, linked conversations, or external issue activity.

Ticket activity history records many of the changes that also create notification context.

### Mentions

Mentions are used when another teammate needs your attention in written context such as a comment, note, or internal update.

Use mentions intentionally. Mentioning someone is stronger than leaving a general comment.

> If notifications feel noisy, review ownership first. Over-assignment and broad mentions usually create more noise than helpful signal.

## Channels and personal accounts

Some notification behavior depends on connected apps and personal accounts.

### Connected accounts

Use **Connected Accounts** or **Apps** when a workspace requires your personal Slack, Telegram, Linear, Jira, or other account connection.

### Workspace channels

Admins configure workspace channels such as Email, WhatsApp, Telegram, Slack, and Microsoft Teams. These channels control where conversations originate and may affect how your team receives updates.

## Keeping notifications useful

Notifications work best when ownership is clear.

### Use assignments

Assign conversations and tickets to the person responsible for the next step.

### Use labels and statuses

Labels and statuses make notifications easier to interpret because they show what kind of work changed and where it sits in the workflow.