---
title: "Notifications"
description: "Every notification DiveLogic raises, what triggers it, and what you can do from the row."
---

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

# Notifications

import { NotificationList, NotificationsBell } from "@/components/react/AccountScreens";

Sixteen kinds of notification exist. Every row is built the same way: what
happened, the detail under it, when it arrived on the right, and any action the
row carries at the foot of it.

## What raises one

| Notification | Raised when | Action |
|---|---|---|
| Plan invite | Someone invites you to a plan, naming the plan and the role | **Accept** opens the plan; **Decline** dismisses it |
| Invite accepted | Someone accepts your invitation | None |
| Invite declined | Someone declines your invitation | None |
| Member left | A member leaves a plan you own | None |
| Allowance running low | Your Tunang usage crosses 80 % of the allowance | **View subscription** |
| Allowance used | The allowance is spent, and "Assistant requests are declined for now." | **View subscription** |
| Subscription changed | Any subscription move: upgrade, downgrade, cancellation, or a change reported by the payment provider | **View subscription** |
| Payment failed | A subscription charge could not be taken, with the amount | **View billing** |
| Application received | An instructor-tier application is submitted | **View subscription** |
| Application approved | An administrator approves it | **View subscription** |
| Application declined | An administrator refuses it, with the reviewer's note or "No reason was given." | **View subscription** |

Accepting a plan invite from the row is the whole flow: no link to follow, no
code to enter. Each allowance notification is raised at most once per allowance
period, not once per request. Of the three application notices, only the two
outcomes reach an applicant.

## Rows you follow up elsewhere

These five appear in the list but do not yet carry their own title or row
action.

| Notification | Raised when | Where to act |
|---|---|---|
| Course invitation | An instructor adds you to a course; accepting is also the data-sharing acknowledgement | **Courses** → Pending enrolments |
| Course removed | An instructor removes a student, or a student withdraws | **Courses** |
| Affiliation invite | You are invited to a business's staff | **Ledger** → Account |
| Invoice issued | An invoice is raised against you and you hold a DiveLogic account | The hosted invoice link in the issuing email |
| Invoice paid | A customer pays an invoice you raised | **Ledger** → Invoices |

A course invitation takes you to the course's own accept screen, never to the
plan-invite flow, because accepting gives your instructor sight of the dives and
reviews you record against that course. Customers without a DiveLogic account
are not notified in the app at all.

## The bell

The bell is an anchored dropdown on wide screens, and opening it marks
everything read, except when a row action navigates you away, which leaves the
rest unread on purpose.

## The notifications page

The Notifications page is the same list full-width on narrow screens, with an
unread count and **Mark all read**. The list holds the most recent 50.

## Next

- [Roles and invites](/account/roles-and-invites) follows the invitation behind
  four of these.
- [Usage allowance](/assistants/allowances) covers the two allowance crossings.

Source: https://docs.divelogic.ai/account/notifications/index.mdx