Skip to content

fix: settings page should provide actionable account controls#5967

Open
SyntaxHQDEV wants to merge 2 commits into
SecureBananaLabs:mainfrom
SyntaxHQDEV:settings-1810
Open

fix: settings page should provide actionable account controls#5967
SyntaxHQDEV wants to merge 2 commits into
SecureBananaLabs:mainfrom
SyntaxHQDEV:settings-1810

Conversation

@SyntaxHQDEV

Copy link
Copy Markdown

Problem

The /settings route rendered a single placeholder card without concrete controls or statuses.

Solution

Added 4 sections with mock data and action buttons:

  • Account & Profile: display name, username, email, profile visibility
  • Notifications: job alerts, messages, marketing preferences
  • Security: 2FA status, active sessions, password age
  • Payout & Billing: payout method, schedule, next payout estimate

Closes #1810

Adds 4 sections to /settings: Account & Profile, Notifications, Security, Payout & Billing.
Uses mock data with status indicators and action buttons matching current frontend style.
github-actions Bot added a commit that referenced this pull request Jun 9, 2026
…nment

- Added fullName as required field in registerSchema
- Removed 'admin' from allowed registration roles
- Prevents users from registering without fullName or as admin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Settings page should provide actionable account controls

2 participants