Real-World Example
Jane opens her profile to confirm the personal identity details connected to her consumer account. The portal should show her ecoAddress details while keeping sensitive identity fields protected and controlled.
Visual Flow
How It Should Work
- It should show the consumer profile details tied to the authenticated account.
- It should show locked identity fields: last name, birth date, and the last four digits of SSN.
- It should protect sensitive fields that should not be freely editable.
- It should keep profile details consistent with account matching and communication flows.
How It Should Not Work
- It should not let the consumer update locked identity fields when those fields are meant to stay fixed.
- It should not expose another consumer profile.
- It should not save incomplete or invalid profile data.
Last modified on July 30, 2026
