> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/notifications.md).

# Notifications screens

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/notifications/README.md).
{% endhint %}

The mobile apps' notification settings and their in-app surveys. Reminders are set in [Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md) and [Create planned task](https://docs.snapfix.com/how-the-apps-work/screens/planner/planned-task.md). Marketing popups show over the group list and the web's Fix page and have no screen of their own here ([Marketing popups](https://docs.snapfix.com/product/features/notifications/marketing-popups.md)). Pushes, device tokens, popups and the survey endpoints are in the [Notifications API](https://docs.snapfix.com/engineering-reference/api/notifications.md).

The two surveys never open in the current apps: their only trigger is commented out, and both apps run Survicate surveys instead ([NPS survey](https://docs.snapfix.com/how-the-apps-work/screens/notifications/nps-survey.md)) \[[ASK-10](https://github.com/snapfix/docs/blob/main/ASK.md#ask-10-which-differences-between-the-ios-and-android-apps-are-intended)].

| Screen                                                                                                         | Platforms    | Where                                                |
| -------------------------------------------------------------------------------------------------------------- | ------------ | ---------------------------------------------------- |
| [Notification settings](https://docs.snapfix.com/how-the-apps-work/screens/notifications/settings.md)          | ios, android | iOS and Android: profile, "Notifications" tab        |
| [NPS survey](https://docs.snapfix.com/how-the-apps-work/screens/notifications/nps-survey.md)                   | ios          | iOS: over the group list when due; never opens today |
| [Product feedback survey](https://docs.snapfix.com/how-the-apps-work/screens/notifications/feedback-survey.md) | ios          | iOS: over the group list when due; never opens today |


---

# 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://docs.snapfix.com/how-the-apps-work/screens/notifications.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.
