35 lines
964 B
Markdown
35 lines
964 B
Markdown
# Feature: User Profile Settings
|
|
|
|
## Status
|
|
|
|
Draft
|
|
|
|
## Goal
|
|
|
|
Allow authenticated users to manage the profile information shown inside the application shell and workspace activity.
|
|
|
|
## User Stories
|
|
|
|
- As an authenticated user, I want to update my name, alias, email, and portrait so that other workspace members see accurate profile information.
|
|
|
|
## Frontend Areas
|
|
|
|
- `/app/settings/user-information`
|
|
- `frontend/src/features/user-profile/`
|
|
|
|
## Backend Modules
|
|
|
|
- Identity
|
|
|
|
## Domain Rules
|
|
|
|
- Profile updates apply only to the authenticated user.
|
|
- Portrait uploads flow through the existing blob storage abstraction.
|
|
- Email changes use the identity module endpoint and should remain auditable through backend identity behavior.
|
|
|
|
## Done When
|
|
|
|
- [ ] User information settings show editable name, alias, and email fields.
|
|
- [ ] Portrait upload remains available from the settings page.
|
|
- [ ] Successful updates refresh the user profile state used by the app shell.
|