> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/collaboration-and-automation/notification-settings.md).

# Notification Settings

### 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

{% stepper %}
{% step %}

### Open settings

Open the profile menu in the top navigation. Select **Settings**.
{% endstep %}

{% step %}

### Open notifications

Select the **Notifications** tab.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Screenshot placeholder: notifications preferences panel with delivery toggles.
{% endhint %}

### 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.

{% hint style="info" %}
Screenshot placeholder: notification bell dropdown with unread items.
{% endhint %}

### Email

Use email when Transform is not open.

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

{% hint style="info" %}
Screenshot placeholder: example email notification.
{% endhint %}

### 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

{% hint style="info" %}
Tip: Treat @mentions as “action required”. Keep them high-signal.
{% endhint %}

### Configure Preferences

For each notification type, pick a delivery method:

* **In-app**
* **Email**
* **Both**
* **Off**

### Starter setup (recommended)

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.

{% hint style="info" %}
Screenshot placeholder: quiet hours selector (start time, end time, days).
{% endhint %}

{% stepper %}
{% step %}

### Turn on quiet hours

Enable **Quiet hours** (or **Do Not Disturb**, depending on configuration).
{% endstep %}

{% step %}

### Set a schedule

Choose start time, end time, and the days it applies.
{% endstep %}
{% endstepper %}

### 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.

{% hint style="info" %}
Following and watching create notifications. Use them intentionally.
{% endhint %}

### Notification History

Past notifications can usually be reviewed from the bell icon.

{% hint style="info" %}
Screenshot placeholder: notification list with timestamps and “Mark all as read”.
{% endhint %}

Retention varies by Account configuration.

Assume older notifications may be archived automatically.

### Troubleshooting

<details>

<summary>Not Receiving Notifications?</summary>

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.

</details>

<details>

<summary>Receiving Too Many Notifications?</summary>

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.

</details>

<details>

<summary>Notifications Delayed?</summary>

* Email digests batch notifications.
* Email delivery can be delayed by the email provider.
* In-app notifications should be near-real-time.

</details>

### Summary

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

Related:

* [Comments and Mentions](/collaboration-and-automation/comments-and-mentions.md)
* [Following and Watching Items](/collaboration-and-automation/following-and-watching-items.md)
* [Comments and History](/collaboration-and-automation/comments-and-history.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/collaboration-and-automation/notification-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.