> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/clarity-lims/clarity-lims-v6.2-and-lablink-v2.4/clarity-lims-v6.2-guide/configuration/user-management/user-and-profile-page.md).

# User and Profile Page

This section describes how to update some of the details associated with your profile, including your password, email address, and profile photo.

After signing into Clarity LIMS, you can update some of the details associated with your profile, including your password, email address, and profile photo.

{% hint style="info" %}
If the user is an LDAP account, then you cannot update the profile in Clarity LIMS.
{% endhint %}

### Update User Profile

1. In Clarity LIMS, at the right of the menu bar, select your username and then select **Profile**.
2. The Profile page opens, displaying the details associated with your user profile.
3. On this page, you can:
   * Change your password.
   * Change your email address.
   * Upload an image to associate with your profile.

### Reset a forgotten password

1. On the **Sign In** screen, click the **Forgot your password** link.
2. In the **Reset Your Password** screen, enter your username or email address and click **Submit**.


---

# 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.bioinsight.illumina.com/clarity-lims/clarity-lims-v6.2-and-lablink-v2.4/clarity-lims-v6.2-guide/configuration/user-management/user-and-profile-page.md?ask=<question>&goal=<user_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.