> 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 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.

<figure><img src="/files/1gxHFmDohVMXESmo5016" alt=""><figcaption></figcaption></figure>

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 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/user-profile-and-account-settings/my-profile-screen.md?ask=<question>&goal=<endgoal>
```

`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.