> 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/how-to/how-to-make-a-list-your-users-can-filter.md). # How to make a list your users can filter Learn how to filter a list in your app! {% embed url="" %} \ First, let’s start by adding a Screen of a simple list to your app. Now, navigate to Components, and add a dropdown menu above your simple list.\ In the tutorial, we’ve already set up the database, so in order to set yours up, you will want to:
* Create a Database Collection for Movies * Within your Movies collection you will need a property for Name (text), Image (image) * Create another Database Collection for Categories * Within your Categories collection, you will need a property for name. Also, we’re going to create a relationship to the Movies collection that is a “many to one” meaning that multiple Categories can belong to one Movie. \ Now, let’s go back to the Simple List and bind it to the Movies Collection. Also, let’s update the Subtitle text to display Magic Text for the Category Name. Next, let’s bind the Dropdown Menu to the Categories Collection.\ Next, we’ll need to set up our filter!\ Click on the Simple List and where it says Filter > All Movies, let’s add a Custom FilterThis will allow us to create an additional filter so that when your users make their selection, it will display below the Dropdown Menu.\ The Custom Filter should be set up to say:Current Movie > Category > NameContainsSelected Category > Name\ And voilà! You’ve got a filter on your Simple List! \ Cloneable Here → --- # 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/how-to/how-to-make-a-list-your-users-can-filter.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.