> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/reminders-and-notifications/notification-settings.md).

# Your notification settings

Choose which emails Pipefile sends you about uploads, comments, completed checklists and expired requests.

These settings control the emails **you** get about your requests. To change what your recipients get, see [Reminders and notification sequences](/reminders-and-notifications/reminder-sequences.md).

Each person on a team has their own settings.

## Change your settings

Open [Account → Notification Settings](https://pipefile.com/dashboard/settings/account#notifications). Turn a switch on or off; the change saves immediately.

## The notifications

| Notification                           | When you get it                                                                              |
| -------------------------------------- | -------------------------------------------------------------------------------------------- |
| **File Upload Notifications**          | A recipient uploads files, or answers checklist items.                                       |
| **New Comment Notifications**          | A recipient or teammate comments on a request. You don't get emails about your own comments. |
| **Checklist Completed Notifications**  | Every item on a checklist has been answered.                                                 |
| **File Request Expired Notifications** | A request expires without being completed.                                                   |

Each one appears twice:

* **Requests sent by me**: requests you sent, or that are assigned to you. All four are on by default.
* **Requests sent by team members**: your teammates' requests. All four are off by default.

## Who gets notified on a team

* **Unassigned request:** the person who sent it.
* **Assigned request:** the assigned teammates, instead of the sender. See [Assign requests to teammates](/requests/assign-requests.md).
* **Everyone else on the team:** only if they turned on the matching **Requests sent by team members** switch, and only for requests they can see. When the **Shared inbox** setting in [Team → General](https://pipefile.com/dashboard/settings/team#general) is off, only team admins can get notifications about teammates' requests. On teams with [user groups](/team-and-account/user-groups.md), you hear about requests from your own groups.

## Notifications without a switch

On requests with forms signed by more than one person, you get an email each time a signer finishes their part. It follows the same rules for who gets notified, and it can't be turned off here.

<details>

<summary>I turned notifications on but nothing arrives</summary>

Check your spam folder, and check whether the request is assigned to someone else: assigned requests notify the assignees, not the sender. See [Emails not arriving](/troubleshooting/emails-not-arriving.md).

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.pipefile.com/reminders-and-notifications/notification-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.