> For the complete documentation index, see [llms.txt](https://taskoncommunitys-organization.gitbook.io/taskon-help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://taskoncommunitys-organization.gitbook.io/taskon-help-center/account-and-system/profile.md).

# Profile

A profile serves as a vital feature for showcasing one's `identity` and `characteristics`. Within TaskOn, having a comprehensive user profile isn't just beneficial for efficiently completing tasks assigned by projects; it's also a crucial means of verifying oneself as an `authentic user`. Projects aspire to ensure that their quest rewards are allocated to genuine user accounts. The initial step towards establishing oneself as a bona fide user is build and refine one's profile page.

**Why Complete Your Profile?**

🔑 **For Security**

* **Non-Wallet Users**: If you signed up via Twitter/Discord, **bind at least 2 social accounts** (Settings → Linked Accounts).
* *Why?* If you lose access to your login method, social bindings let you recover your TaskOn account and linked wallets.
* 🚨 **Unbound profiles risk permanent asset loss** if credentials are compromised.

🎯 **For Higher Rewards**

* Projects prioritize users with **verified social identities**
* The more accounts you link, the more you appear as a real person, and the more likely you are to gain potential rewards in the screening process.

Here are some `tips` on how to edit your profile:

{% embed url="<https://taskoncommunitys-organization.gitbook.io/taskon-help-center/~/changes/X2eW5udRG1h0wgE3Ix0C/profile/edit-profile>" %}

{% embed url="<https://taskoncommunitys-organization.gitbook.io/taskon-help-center/profile/multi-addresses>" %}

{% embed url="<https://taskoncommunitys-organization.gitbook.io/taskon-help-center/profile/bind-and-unbind>" %}


---

# 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://taskoncommunitys-organization.gitbook.io/taskon-help-center/account-and-system/profile.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.