---
title: Notifications
description: What Laver tells you about, in the app and by email, and how to turn each of it off.
section: Administration
order: 6
---

# Notifications

Laver notifies you about five things. Each one can arrive **in the app** and
**by email**, and you control the two independently.

| Event                                       | Group   |
| ------------------------------------------- | ------- |
| A ticket is assigned to me                  | Tickets |
| Somebody mentions me                        | Tickets |
| Somebody replies on a ticket I commented on | Tickets |
| A sprint starts                             | Sprints |
| A sprint is about to end                    | Sprints |

## Choosing what reaches you

**My profile → Notifications.** Every event has an in-app tick and an email
tick, and both start on.

Preferences are stored sparsely: a record exists only where you have changed
something. That has one deliberate consequence — **an event added in future
starts switched on** for everyone, rather than being silently muted for anyone
who has never opened the screen. If you want it off, turn it off.

Turning a channel off stops it being produced at all, so muting an event does
not quietly accumulate a pile of unread notifications you never see.

## Emails

An email carries the ticket, who did the thing, and a link straight to it.

Each one has an **unsubscribe** link, and mail clients that support RFC 8058
show their own unsubscribe button for it.

**The unsubscribe link is one decision, not one category.** Clicking it stops
_all_ optional email — notification email and billing/product updates together.
Somebody clicking "unsubscribe" means stop the optional email, not stop this
kind and keep the rest arriving. You can resubscribe from the same link.

**What it does not stop.** Security notices and the non-payment sequence ignore
it by design: a password change or a failed payment reaches you whatever your
preferences say. Those are not marketing, and losing a customer silently
because they muted an invoice is worse than an unwanted email.

If you want to keep billing email but stop ticket email, use the per-event
email ticks in your profile rather than the unsubscribe link.

## By API

```bash
curl https://api.laver.app/profile/notification-preferences \
  -H "Authorization: Bearer $SESSION_TOKEN"
```

Returns every event with its label, its group, and the state of each channel,
so a client can render the screen without hard-coding the list.

`PUT` the same path to change them. This is a session-token route — an API key
cannot read or change someone's preferences.

## What there is not

- **No push notifications** and no PWA delivery yet.
- **No digest.** Emails are sent per event, not batched into a daily summary.
- **No per-board or per-workspace override.** A preference is per person,
  across everything they can see.
