For the complete documentation index, see llms.txt. This page is also available as Markdown.

Notification Settings

Tune alerts so you get the signal, not the noise.

Overview

Notification settings control notification types and delivery timing.

They reduce interruptions while keeping action-required signals visible.

Key Concepts

  • Delivery channel: in-app, email, or browser notifications

  • Notification type: event category, such as mentions or assignments

  • Quiet hours: schedule that suppresses non-urgent alerts

How It’s Used

Use settings to prioritize mentions and assignments.

Use quiet hours to prevent off-hours noise.

Benefits

  • Faster response to high-signal changes

  • Lower interruption cost during execution work

  • Cleaner governance through consistent follow-through

Setup Steps

1

Open settings

Open the profile menu in the top navigation. Select Settings.

2

Open notifications

Select the Notifications tab.

Screenshot placeholder: notifications preferences panel with delivery toggles.

Delivery Channels

Most Accounts support at least in-app notifications.

Some also support email and browser notifications.

In-app

Use the bell icon to view alerts.

In-app alerts can link directly to the item that changed.

Screenshot placeholder: notification bell dropdown with unread items.

Email

Use email when Transform is not open.

If digests are available, use them to batch non-urgent alerts.

Screenshot placeholder: example email notification.

Desktop (optional)

If enabled, these are browser push notifications.

Browser permissions must allow notifications for Transform.

Notification Types

Account configuration may expose different notification types.

Common categories:

  • Assignments: assigned/unassigned

  • Comments: new comments and replies

  • Mentions: when someone tags you with @

  • Status and field changes: status, priority, due dates

  • Dependencies: a blocking item is cleared

  • Project changes: added to a project, project status updates

Tip: Treat @mentions as “action required”. Keep them high-signal.

Configure Preferences

For each notification type, pick a delivery method:

  • In-app

  • Email

  • Both

  • Off

Start lean. Add more only when signal is missing.

  • @mentions → In-app + Email

  • Assigned tasks → In-app + Email

  • Comments on items I own → In-app

  • Status changes and general project updates → Off (for most roles)

Quiet Hours (Do Not Disturb)

Quiet hours pause or delay notifications during off-hours.

Screenshot placeholder: quiet hours selector (start time, end time, days).

1

Turn on quiet hours

Enable Quiet hours (or Do Not Disturb, depending on configuration).

2

Set a schedule

Choose start time, end time, and the days it applies.

Reduce Notification Noise

If alert volume is high, apply these steps in order:

  1. Keep @mentions and assignments.

  2. Turn off comment notifications for items you only watch.

  3. Switch email to digest mode, if available.

  4. Unfollow items that do not require awareness.

Following and watching create notifications. Use them intentionally.

Notification History

Past notifications can usually be reviewed from the bell icon.

Screenshot placeholder: notification list with timestamps and “Mark all as read”.

Retention varies by Account configuration.

Assume older notifications may be archived automatically.

Troubleshooting

Not Receiving Notifications?
  1. Confirm notifications are enabled for that event type.

  2. Confirm the Teammate is a follower or assignee (if required).

  3. If using email, verify the email address on file and check spam/junk.

  4. If using desktop notifications, check browser permissions.

Receiving Too Many Notifications?
  1. Turn off low-signal types (status churn, broad project updates).

  2. Use digests for email (if available).

  3. Unfollow items that do not require awareness.

  4. Use quiet hours.

Notifications Delayed?
  • Email digests batch notifications.

  • Email delivery can be delayed by the email provider.

  • In-app notifications should be near-real-time.

Summary

Notification settings should prioritize action-required events and suppress low-signal churn.

Related:

Last updated