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

# Notifications

> Assignments, approvals, expirations, and reminders reach the right people over in-app, email, and Slack, with per-user opt-outs by topic for email and Slack.

A notification alerts one person to an assignment, approval, expiration, or other event. Alforse can deliver it through the **in-app inbox** (the bell in the top bar), **email**, and **Slack**. In-app delivery is always enabled; users can mute email and Slack by topic. Alforse does not notify users about their own actions.

## What raises a notification

FieldType

<details>
  <summary>**Assignments**</summary>

  Someone is put on a record (job, order, RFQ, invoice, issue, risk, procedure, picking list, stock transfer, dispatch, training). The assignee is the recipient.
</details>

<details>
  <summary>**State changes & responses**</summary>

  An approval was **requested**, **approved**, or **rejected**; a job **completed**; a change notice entered a new stage; a quote **expired**; a customer or supplier responded to a digital or supplier quote.
</details>

<details>
  <summary>**Expirations & reminders**</summary>

  Time-driven, raised by scheduled jobs: a **gauge calibration expired**, a **maintenance dispatch** was auto-created, or the weekly **training reminder** rolls up a person's outstanding trainings. Accounting sync failures also raise a notification (see [accounting integrations](/docs/integrations/accounting.md)).
</details>

<details>
  <summary>**Workflow**</summary>

  A [workflow](/docs/reference/workflows.md) reached a **"Notify someone"** step. This is the only notification with user-defined wording, and it uses the **General** topic.
</details>

NOTE

Notifications are informational. Marking one as read does not change the underlying record or complete an approval.

## Topics and channels

Every event maps to one **topic**, which controls inbox grouping and channel preferences: Approval, Job, Sales, Quote, Purchasing, Inventory, Quality, Maintenance, Training, Suggestion, Items, General, or Changelog. The settings page lists twelve rows: every topic except **Items**, which has no toggle. The **Changelog newsletter** row is email-only and off until you turn it on.

The channels differ in what they require:

FieldType

<details>
  <summary>**In-app**</summary>

  The bell in the top bar. **Always written**, for every recipient, on every event — it cannot be turned off.
</details>

<details>
  <summary>**Email**</summary>

  A per-notification email with a **View** button. Sent only when the company's plan includes email notifications.
</details>

<details>
  <summary>**Slack**</summary>

  A DM in the connected workspace. Needs an active Slack integration *and* a matching Slack account for the recipient.
</details>

## Muting a topic

Each user controls their own email and Slack delivery under **Account → Notifications**: a grid with one row per topic, a column per channel, a switch in each cell. In-app has no switch.

Alforse screenshot**Account → Notifications preferences grid: topic rows, Email and Slack columns, switches per cell**

Muting is per topic, per channel, per company. The in-app inbox always gets everything.

Each channel is enabled by default (except the Changelog newsletter). Turning off a switch mutes only that topic and channel for the current company. For example, muting Purchasing in Slack does not mute Purchasing email, other Slack topics, or notifications in another company. The Slack column appears only when Slack is connected. The email column always appears and indicates when the plan does not support delivery.

## Who receives an expiration or reminder

Assignment events notify the assignee. Time-driven events derive recipients as follows: an expired gauge calibration notifies the user list in [calibration](/docs/reference/calibration.md) settings, an automatically created dispatch notifies all employees at its work center, and the weekly training reminder sends each person a digest. Alforse has no general notification-group entity; only calibration expiration uses a configured list.

## The inbox

The bell opens the inbox, with **Inbox**, **Trainings**, and **Archive** tabs: recent notifications newest-first with an unread count, each row carrying an icon, a short description, who it came from, and a timestamp. Click through to the record, mark a row read, or use **Archive all**.

## Related

**Approvals**

Requested, approved, and rejected each notify the approvers or the requester.

[Open](/docs/reference/approvals.md)

**Calibration**

A lapsed calibration notifies the configured group.

[Open](/docs/reference/calibration.md)

**Workflows**

Compose your own notification from a "Notify someone" step.

[Open](/docs/reference/workflows.md)

**Webhooks**

For machine-to-machine events rather than a person's inbox.

[Open](/docs/building/webhooks.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.