> 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/overview-screens-database-layout-settings-use-cases.md). # Overview — Screens, Database, Layout Settings, Use Cases The Browse Users feature template is perfect for any community app where users are able to see who else is using the app and interacting in some sort of way — think forums, messaging, events, and more! This feature template comes with a beautifully designed profiles screen and member list to quickly spin up a browsing feature for your app. ## Screens Overview: 📚 **Instructions Screen** Quickly get an overview of the template with quick tips, a help doc, and associated templates that may be of interest. *This screen may be deleted at anytime.* ### User Screens 🚻 **Browse Members Screen** This screen contains all members of the app for users to scroll and find someone. 👤 **Profile Screen** This screen contains all information related to someone that is available to view by other users. ## Database Overview The Browse Users Feature Template comes with a database that contains sample data. Each Adalo database contains Collections and each collection comes with the associated Properties. Any necessary relationship between the collections is set up, as well. {% hint style="info" %} **Important Note About the Database:** If you **delete** a Collection or Property from the Feature Template, this could impact the functionality of your app. If you **add** a Collection or Property to your Feature Template, this will not impact the functionality of your app. {% endhint %} Below is an outline of the included Collections and their Properties. The Collection name is bolded and includes a description. The Properties include their name, property type (in brackets), and a description. ### Basic Collections & Properties #### 👥 **Users** The Users Collection automatically comes with every Adalo app. This collection will hold all the information related to anyone who uses the app. This information is initially collected from a user when they sign up to use your app. * Email \[Text] — the user’s email address. * Password \[Encrypted] — the user’s password to log into the app. This cannot be viewed by anyone, including the administrator. * Username \[Text] — the user’s username. * Full Name \[Text] — the user’s first and last name. * Profile Photo \[Image] — the user’s profile picture. * User Bio \[Text] — a bio written by the user. * Rating \[Number] — a user’s skill level rating. * Games Played \[Number] — the number of games the user has played. ## Layout Settings Each screen in the Browse Users Feature Template is created using responsive design. The screens will look good on any device or tablet. Most screens have been designed with Custom Layouts. If you add a new component to a screen, you might notice that the other screen sizes are impacted. ### Layout Overview To view or edit the layout for different screen sizes — click the Screen title to reveal the dropdown.
The default view for this template is Desktop. When you change the screen size for one screen in the Builder, it does not change the screen size of the rest of the screens on the canvas. #### Hidden Components
In each view, there may be components that do not appear on Desktop, but are visible on Mobile. These are grayed out in the lefthand panel & denoted with an icon. Another way to view which device components are visible on is the Layout Tab here:
#### Custom Layout
Some components come with custom layouts based on screen size. To view those settings, check the Layout Tab & scroll to the Custom Layout Settings. ## Example Use Cases: * A Pickleball club can show all members to coordinate games and tournaments. * A business can create a forum to help its members connect and use their product. * A daycare center can showcase their employees for parents to get to know better. * and many more! --- # 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/browse-users/overview-screens-database-layout-settings-use-cases.md?ask=&goal= ``` `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.