Workspace settings
Admin lives outside daily production.
A focused area for account profile, render defaults, and governance. The current MVP keeps these controls descriptive until authenticated server persistence exists.
History is stored in the browser; catalog presets come from the try-on API. Team, billing, and roles need backend account models before becoming editable.
Profile
Workspace identity
Default name, brand context, and account ownership for catalog teams.
Defaults
Render preferences
Controls that should eventually prefill the workspace without hiding per-run choices.
Governance
Review policy
Future location for approvals, role access, retention, and export rules.
Server-backed history
Persist generated outputs by workspace instead of browser storage.
User and team roles
Protect dashboard pages and separate operators from admins.
Saved render presets
Let teams define default model, pose, scene, and quality combinations.
Queue observability
Expose pending, processing, failed, and completed jobs from the backend.
Page discipline
No operator overload
Settings stays intentionally separate from creation and review. Operators complete daily catalog work without seeing admin concepts unless they choose this page.