> For the complete documentation index, see [llms.txt](https://help.roolz.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.roolz.net/en/user-profile/what-is-a-user-profile/how-to-change-user-profile-information.md).
# How to change user profile information?
{% stepper %}
{% step %}
In the upper right corner, click on your avatar (or circle with two letters);
{% endstep %}
{% step %}
Click "My profile" from the drop-down menu. Your profile view page will be opened;
{% endstep %}
{% step %}
Click "Edit".
{% endstep %}
{% step %}
In the edit mode, you can change information, such as:
1. **Photo** — people trust users more if they have a real photograph;
2. **First Name\*** — maximum 25 characters;
3. **Surname\*** — maximum 25 characters;
4. **Middle name —** maximum 25 characters;
5. **Nickname\*** — A-Z, 0-9 and \_ are allowed. Length from 4 to 20 characters. Nickname must be unique, i.e. different from the nicknames of other users registered on the platform;
6. **Country** — displayed as the flag of the country where you live;
7. **About** — a brief description of yourself, your experience, accomplishments and services;
8. **Contact information** — personal and business phone number, personal and business email;
9. **A** **link** to your company's website.
\*Required fields
{% endstep %}
{% endstepper %}
---
# 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.roolz.net/en/user-profile/what-is-a-user-profile/how-to-change-user-profile-information.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.
