> 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/user-profile-and-account-settings/setup-step-2-screen.md).
# Setup Step 2 Screen
This unique profile creation step is great if you want to collect information about a user that is similar to a multi-select question with pre-defined options.
This step in profile creation is controlled by a second collection in the database. The relational nature of the collection to the users collection allows for each user to multi-select options to give the administrators more information about the people using their app.
In this case, users are selecting their interests from a list.
## The Components
### **List Component**
This is a list of ‘Interests’ as specified in the Interests Collection.
The toggle shows a checked circle if the Logged In User is included in that list items Users. The toggle is the ⚡ **Action** for this component.
### Next Button
⚡ **Button Action**
* Link Action to ‘Setup Step 3’ 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/user-profile-and-account-settings/setup-step-2-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.
