Layout
Composition principles
Keep record identity, owner, status, and next action together. Separate verified account facts from derived health indicators and keep activity chronological.
Salesforce Lightning Design System / Published template
CRM Account Health Overview
A record-oriented workspace for reviewing an account, its active work, relationship context, and accountable next steps.
Prompt reference v1
Preview
Structure blueprint
A compact record header establishes identity and status, followed by key relationship facts, open work, recent activity, and a focused next-step panel.
Interaction
Behavior and access
Record actions use explicit labels and confirmation where consequences are material. Collapsible sections retain accessible names, and status is never conveyed by color alone.
Implementation
Engineering boundaries
Compose the view from server-provided account DTOs. Preserve stable record IDs, show source timestamps, and do not derive commercial commitments or account status inside UI components.
Design system
Salesforce Lightning Design System token ledger
Salesforce's public design system for enterprise application experiences.
Color roles
- model
- semantic interface roles
- requiredRoles
- background, text, brand, success, warning, error
Typography
- approach
- enterprise information hierarchy
- requirements
- compact record metadata, clear action labels
Spacing
- approach
- record-oriented layout
- baseUnitPx
- 4
Component rules
- actions
- Separate global, object, and record-level actions.
- records
- Group identity, status, ownership, and next actions consistently.
Classification