> 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/search-messages-screen-and-channels-screen.md).

# Search Messages Screen & Channels Screen

The Search Messages Screen and the Channels Screen contain two main components that control all the functionality.

## The Components

### **Input Fields**

<figure><img src="/files/kpjgJz0tVEnQWsWFuuVu" alt=""><figcaption></figcaption></figure>

Each screen contains an input field that will begin to filter the list as soon as a user starts to type into it.

### **List Component**

Each list contains information regarding either Messages or the available Channels. Each list is filtered by the text that appears in their connected “Inputs” on the screen.

⚡ **Actions**

The Channel Screen:

* On each list item
  * ⚡ Update Logged In User > Active Channel > Channel ID. This will ensure the User sees the channel they clicked on when they return to the Messages Screen
  * ⚡ Update Logged In User > Channels > Add Current Channel *but only when* the “Current Channel > ChannelUsers” does not contain the Logged In User.
  * ⚡ Link Action to the ‘Messaging’ Screen

{% hint style="danger" %}
Similar to visibility rules for components, there are conditional actions. To denote whether or not something has a conditional action — you will notice ✨ on the icon.

<img src="/files/L7bK0fTQBR06Gzs3FlP5" alt="" data-size="original">

If you make edits to these actions, check for conditional logic that may be applied:

<img src="/files/37XmbdJN1NkTuxJf1IHs" alt="" data-size="original">

This can be found under “ADVANCED” in the settings of an action.
{% 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 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.adalo.com/feature-templates/group-messaging/search-messages-screen-and-channels-screen.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.
