> 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/my-profile-screen.md).
# My Profile Screen
The User Profile Screen is integral to any app that has users that will interact with each other. This is a quick way to see users of an app and get an overview of their information.
The User Profile Screen displays information about the user of an app in an easy-to-digest way. From a user bio to their profile picture and everything in-between, this screen is simply an overview of each individual user in the app.
There are no unique components on this screen — however, there are datapoints for the users that will be displayed that are NOT collected during the sign up process. These datapoints are shown on this screen and must be filled in by the admin via Adalo for each user.
These properties can easily be added to the profile creation (Setup Step 1) by adding visible fields to the Rating and Games Played properties in the User Collection.
⚡ **Button Actions**
* Link Action to ‘Account Settings’ Screen from the Edit My Profile Button
---
# 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/my-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.
