Notifications must be enabled for your organization. Contact your Gradial team to get access.
What Notifications Enable
In-app notification inbox
A dedicated sidebar tab alongside Home and Chats. Mark notifications read or unread, archive them, and scroll through your full history. Sort and filter preferences are saved per user across sessions.
Real-time banners
Task status changes surface as live in-app banners the moment they happen — no refresh needed. Banner delivery respects your per-event channel preference.
Email notifications
Branded task notification emails delivered for enabled events, with the task title, a summary, your workspace, and a deep link back to the task thread.
Per-event channel control
Choose Banner, Email, or None for each of the five task events. Set organization-wide defaults as an admin, and let individuals override their own preferences.
Task subscribers
Assignees and approvers are subscribed automatically. Anyone can be added manually from the task header. Subscribers are who gets notified.
Five task events
Created, Kicked off, Needs attention, Ready for review, and Unblocked — the moments that actually require a response.
How It Works
When a task changes to a covered status, Gradial creates a notification for each subscriber. That notification drives both the in-app inbox entry and, if enabled for that event, the email delivery. Because both channels share the same source, email and in-app notifications stay consistent. In-app banners appear immediately. Email is delivered by a background job that processes in near-real-time — expect a short delay between the status change and the email landing.Channel Types
| Channel | What it does |
|---|---|
| Banner | Shows an in-app toast and creates an item in the Notifications inbox |
| Sends an email notification and also creates an item in the Notifications inbox | |
| None | Silences notifications for that event — no banner, no email, no inbox item |
| Org default | Uses the organization’s default setting for that event (the default for all users until they set a personal override) |
Common Use Cases
Approver pulled in at the right moment. A task reaches Ready for review. The approver — automatically subscribed — gets an email and an in-app banner, and can act without hunting for the thread. Author unblocked. A task that was waiting on a dependency becomes Unblocked. The assignee sees it surface in their inbox and picks the work back up immediately. Needs-attention escalation. A running task hits a state that needs input. The subscriber is notified so the task doesn’t sit stalled without anyone knowing. Org admin sets team policy. An admin configures org-default channels per event — email on Ready for review, banner-only on Created — so the whole team starts with sensible defaults. Individual tunes their own noise. A user switches Created and Kicked off to None for themselves while keeping Ready for review on email, overriding the org default just for their account.Configuration
Admin setup
- Contact your Gradial team to enable the
notificationsflag for your organization. - Navigate to Settings → Notifications as an org admin.
- Set the organization-default channel for each event. These defaults apply to all users until they set a personal override.
Personal preferences
Each user can override the org defaults for their own account from Settings → Notifications. Org defaults remain visible but are read-only for non-admins.Default behavior
Out of the box, banners are on and email is off for each event. Users inherit the org default until they set a personal override.Permissions
| Action | Required role |
|---|---|
| Set org-default channel preferences | Org admin |
| Set personal channel preferences | Any user (for their own account) |
| View org defaults | Any user (read-only for non-admins) |
Limitations
- Task notifications only — not arbitrary app activity, comments, mentions, or non-task threads.
- Two channels — in-app banner/inbox and email. No Slack, SMS, mobile push, or webhook delivery.
- Five fixed event types — users choose channels per event but cannot define custom events or trigger conditions.
- Email is not instant — processed by a background job in near-real-time batches; the in-app banner is the immediate channel.