> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation-1/account-management/profile-personal-settings/managing-password.md).

# Managing Password

Users can change their password in the **Personal Settings** section by navigating to the **Change Password** tab. This feature empowers users to maintain the security and integrity of their accounts by periodically updating their passwords.

<div align="left"><figure><img src="/files/Q26nV5oW8A4nL8VoShf6" alt=""><figcaption></figcaption></figure></div>

## Password Requirements

All of the listed requirements must be met to create an acceptable password.

* a minimum of 12 characters
* one lowercase character
* one uppercase character
* one number
* one special character

{% hint style="info" %}
Users can access the password requirements within the platform by clicking on the "?" next to the "Enter New Password" label.&#x20;
{% endhint %}


---

# 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://docs.plextrac.com/plextrac-documentation/product-documentation-1/account-management/profile-personal-settings/managing-password.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.
