Access boundary: Authenticated browser session.
Implemented Classic/V2 personal appearance without new business authority.
Surfaces: Authenticated web Classic/V2; native reads preference without a setter; no new business API/MCP authority.
Read the engineering guide · All features
Capabilities
- Full real-web Classic/V2 views with the same account, tenant, resources and operations
- Account at navigation bottom, appearance beside language, applied after a successful profile save; mobile identity/role remain visible with the menu closed
- Personal users.preferred_dashboard_appearance, migration 0053, classic default and cross-workshop/session/device reconciliation
- Strict browser account PATCH with current authority, Origin/CSRF and field-name audit; every role changes only its own preference
- Temporary appearance=v2/classic override accepts legacy atelier URLs, never persists server-side and clears after explicit appearance save or identity change; local cache is non-authoritative
- Existing activity/alerts precede introduction, otherwise a complete welcome; content preview precedes approval in reading/tab order
- Stable PDF review frame across loading/render/error, keyboard-accessible internal scrolling and unchanged consent/data authority
- Consistent documents, preparation, review, tracking, assistants, account, studio, Horizon, credits, tables and forms; Belvédère remains a distinct platform surface
- One brand signature, workshop in navigation and no redundant V2 footer; service status near account and browser timezone near dates
- One page title, contextual detail back link and task-specific primary action; global New dispatch stays secondary and permission-aware
- Generation introduction focuses on finding PDFs and makes clear that generation sends nothing
- Official portrait/wordmark, approved engravings and blue swallows used sparingly on home, empty documents and assistants
- Four-language labels; simulation notices only for simulated sessions
- Same four roles, supervisor options, private access and consents; no new mandate, channel or business API/MCP tool
- Native account/session reads include appearance without a setter; existing name/language browser PATCH and native language PATCH remain compatible