> 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/browse-users/browse-members-and-profile-screen.md).
# Browse Members & Profile Screen
The Browse Users Feature Template comes with two unique screens — one to view all members and one to view each member in detail.
The simple flow of browsing members is found in several different apps and consists of two screens — one with a list of all the members and another to view the details of that particular user.
Most components inside this Feature Template are dynamically controlled by Magic Text and pull information from the Users Collection.
{% hint style="warning" %}
There is information about each user that is not collected during sign up — like profile photo, rating, games played, user bio, etc. So if you would like the user to enter that information, please add a form component somewhere to collect that information.
{% 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/browse-users/browse-members-and-profile-screen.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.
