> 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/group-messaging/edit-message-modal-screen-and-edit-channel-modal-screen.md).

# Edit Message Modal Screen & Edit Channel Modal Screen

Each of the Edit Screens within the Group Messaging Feature Template allow the Logged In User to update or delete information in the database.

The Edit Message Modal Screen allows the Logged In User to update or delete messages that have been sent in a given channel, while the Edit Channel Modal Screen allows the Logged In User to update or delete the Channel name within the application.

Each of these screens follows a similar pattern where there is information that is available to be edited and subsequent actions to update or delete the data depending on the button a user clicks.

### **Data**

Since the data is coming from a particular list item — known as “Current Collection Item” — the text that will initially appear is the “Current” data that appears in the database for that particular item. A user is then able to update that text and the changes will be reflected once a button is clicked with the appropriate actions.

⚡ **Actions**

1. UPDATE: The purple UPDATE buttons on both screens contain an Update Action for the Current Item within the database.
2. DELETE: The gray DELETE text on both screens contain a Delete Action for the Current Item within the database.
3. CANCEL: The white CANCEL buttons on both screens contain an Update Action, to reflect the text in each input and a Link Action “Back” to the previous screen.


---

# 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/group-messaging/edit-message-modal-screen-and-edit-channel-modal-screen.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.