> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/feature-templates/announcements-and-notifications/notify-all-and-notify-one-screens.md).
# Notify All & Notify One Screens
The Notify All & Notify One Screens allow Admins to create notifications that will be sent to all, or one of, their apps users and review all the notifications that have been sent before.
Notifications are an important feature in any app to keep your audience engaged and informed. These particular screen within the Announcements & Notifications feature template allows an Admin to create and sent a notification to all the users of their app, or one.
You may need to send notifications to all users about an upcoming event or a notice of a service interruption — while the Notify One feature can be used to update a single user on their payment status.
Both screens are made up of similar components including a form component and a list component to display previously sent notifications.
## The Components
### **Horizontal Navigation**
This navigation is used to switch between the ‘Notify All’ Screen and the ‘Notify One’ Screen.
⚡ **Actions**
* On each screen, the opposite screen name is linked back to.
* Notify All text is linked to Notify All Screen
* Notify One text is linked to Notify One Screen
### Form Component
⚡ **Submit Button Actions**
* Create Notification
* Trigger Notification
* Recipient > All Users on the ‘Notify All’ Screen
* Recipient > Logged In User > Notifications > Target User
### List Component
⚡ **Icon Action**
* Delete Notification
{% hint style="danger" %}
Unlike the ‘Dismiss Notification’ action on the users side — the list on the Admin side will delete the notification completely from the database.
{% endhint %}
---
# 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://help.adalo.com/feature-templates/announcements-and-notifications/notify-all-and-notify-one-screens.md?ask=&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.
