> ## Documentation Index
> Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Change Password

> Allow users to securely update their login credentials.

## Purpose

Provides authenticated users with the ability to update their password while maintaining account security.

## Quick Summary

* Users must know their current password.
* New passwords must meet password requirements.
* Password confirmation is required.
* Users may only change their own password.

## Workflow

```mermaid placement="top-right" actions={true} theme={"system"}
flowchart TD
    A["User Opens Change Password"]
    A --> B["Enter Current Password"]
    B --> C["Enter New Password"]
    C --> D["Confirm New Password"]

    D --> E{"Validation Successful?"}

    E -->|No| F["Display Validation Error"]
    F --> C

    E -->|Yes| G["Password Updated"]

    classDef process fill:#F8FAFC,stroke:#64748B,stroke-width:1.5px,color:#0F172A;
    classDef decision fill:#FEF3C7,stroke:#D97706,stroke-width:2px,color:#78350F;
    classDef error fill:#FEE2E2,stroke:#DC2626,stroke-width:2px,color:#7F1D1D;
    classDef outcome fill:#DCFCE7,stroke:#16A34A,stroke-width:2px,color:#14532D;

    class A,B,C,D process;
    class E decision;
    class F error;
    class G outcome;
```

## Password Requirements

The new password must:

* Be different from the current password
* Meet platform password requirements
* Match the confirmation field

# Real-World Example

Sarah logs into the Creditor Portal and wants to update her password.
She:

* Enters her current password
* Enters a new password
* Confirms the new password
* Saves changes
  The system validates the request and updates her credentials.

## How It Should Work

* Require current password validation.
* Require password confirmation.
* Enforce password complexity rules.
* Update only the logged-in user's password.
* Allow continued use of the application after a successful change.

## How It Should Not Work

* Allow password changes without the current password.
* Accept weak passwords.
* Accept mismatched confirmation values.
* Change another user's password.

## Developer Notes

* Password changes must be scoped to the authenticated user.
* Password history and security rules should be enforced consistently.
* Authentication state must remain secure throughout the process.