The job of this console
Clear unread, jump to the record, act there, mark read. Dismiss noise; do not rebuild work from the alert text.
Workspace · Notifications
Notifications
Alerts, mentions, and system updates that deep-link to the record that changed — not a second inbox of work.
Scroll to Flowcharts. Scenario: Manage notifications and alerts.
Event list
Pings that already happened on a source record
Notifications are a reading surface on domain events. Opening one should land you on leave, a task, a ticket, or an approval — not on a message that is the only copy of the decision.
Workspace → Notifications
Route
/workspace/notifications
Org flag notificationsEnabled
All signed-in personas
Seat at the table
Everyone with notificationsEnabled. Admins still author templates. Workflows may generate the event.
The working rhythm
Open the center or bell, click through, finish on the source screen, return only for the next unread.
Moments that bring you here
After submit. A mention. SLA mail. When the bell is red and you do not know which module moved.
ⓘ
Events, not work items
A notification never replaces Task, leave, or paycheck. Templates supply copy; sources supply truth.
Flowcharts
1 — Read and jump
Open an unread alert and land on the source record.
flowchart TD
A[Open Notifications] --> B[Scan unread]
B --> C[Open an alert]
C --> D[Land on source record]
D --> E[Act there]
E --> F[Mark read]
- 1OpenWorkspace → Notifications or the bell.
- 2ScanUnread project, approval, and mention items.
- 3JumpDeep link opens the owning screen.
- 4ActApprove, comment, or dismiss from the source.
Overview
The notification center lists events already written by leave, timesheet, tickets, workflows, and similar. Copy still comes from notification templates. Preferences live on profile.
How to use
1. Jump, then act
Do not treat the list as a todo database.
2. Templates own wording
Bad subject lines are Admin → Notification templates.
3. Profile for channels
Email vs in-app is not configured on this register.