Notifications

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

A alerts one person to an assignment, approval, expiration, or other event. Carbon 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. Carbon does not notify users about their own actions.

What raises a notification

FieldType
Someone is put on a record (job, order, RFQ, invoice, issue, risk, procedure, picking list, stock transfer, dispatch, training). The assignee is the recipient.
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.
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.
A workflow reached a "Notify someone" step. This is the only notification with user-defined wording, and it uses the General topic.
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, or General. The settings page exposes eleven topics; Items has no toggle.

The channels differ in what they require:

FieldType
The bell in the top bar. Always written, for every recipient, on every event — it cannot be turned off.
A per-notification email with a View button. Sent only when the company's plan includes email notifications.
A DM in the connected workspace. Needs an active Slack integration and a matching Slack account for the recipient.
HEADS UP

Email is plan-gated: companies without the EMAIL_NOTIFICATIONS plan feature skip the email channel entirely, regardless of the per-user switch. Slack has no plan gate — it only needs the integration. See licensing.

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.

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

Each channel is enabled by default. 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 settings, an automatically created dispatch notifies all employees at its work center, and the weekly training reminder sends each person a digest. Carbon has no general notification-group entity; only calibration expiration uses a configured list.

The inbox

The bell opens the inbox: 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, or mark a row read.