Design Principle
Profile, login security, notifications, and billing have different risk levels and should be separated.
Principle
Profile, login security, notifications, and billing have different risk levels and should be separated.
Design action
Profile fields support autosave or explicit save; security and billing use stronger confirmation, and notification preferences use grouped toggles.
Examples
Positive example: Account pages, member profiles, team settings, and personal preferences. Counterexample: Avatar edit and account deletion have the same visual weight.
Apply when
Account pages, member profiles, team settings, and personal preferences. Users need to judge state, scope, risk, or next action quickly.
Source notes
Source note: Synthesized from GOV.UK, Carbon, Polaris, Atlassian, Design.Systems, Design Systems Repo, and product-pattern libraries. GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Carbon Patterns: https://carbondesignsystem.com/patterns/ Shopify Polaris: https://polaris-react.shopify.com/ Atlassian Design System: https://atlassian.design/ Design Systems Repo: https://designsystemsrepo.com/
Agent Directive
Profile fields support autosave or explicit save; security and billing use stronger confirmation, and notification preferences use grouped toggles.