ZEVA 2 - BCEID User Dashboard

**Describe the task**
Design and implement an BCEID User Dashboard that provides a centralized overview of the user’s activity within the system.
The dashboard must include: User Information Panel and Action Center
The Action Center must be divided into three sections:
1. Requires Action
2. In Progress
3. For Awareness
Each section contains grouped activity types (modules), which can be expanded to show individual actionable items.

**Design**
[Link to wireframes](https://www.figma.com/design/7Qgou3rxcHHk5qbmD9538x/ZEVA-2?node-id=1980-21166&t=mZeVI7qJNES4BuLi-1)
Figma designs include:
Full dashboard layout ([collapsed](https://www.figma.com/design/7Qgou3rxcHHk5qbmD9538x/ZEVA-2?node-id=1980-21168&t=mZeVI7qJNES4BuLi-1) and [expanded](https://www.figma.com/design/7Qgou3rxcHHk5qbmD9538x/ZEVA-2?node-id=1981-21597&t=mZeVI7qJNES4BuLi-1) states)
Expandable component behavior[ (separate component link provided)](https://www.figma.com/design/7Qgou3rxcHHk5qbmD9538x/ZEVA-2?node-id=1547-3909&t=mZeVI7qJNES4BuLi-1)
Examples of activity labels and CTA text

**Purpose**
The goal of this dashboard is to:
Provide users with a clear, prioritized overview of their tasks and system activities
Enable users to quickly understand what requires action vs what is in progress vs completed

**Acceptance Criteria**
- [ ] Dashboard Structure: User information panel (left side) and Action Center (main content area)
- [ ] Requires Action Block. Includes all items where user action is required: Drafts (e.g. saved but not submitted)/ Returned items/ Rejected items/ Requests for additional information
- [ ] In Progress Block. Includes items that: Have been submitted/ Are under review BC Gov or other suppliers / Do not require user action at the moment
- [ ] For Awareness Block. Includes completed items: Approved submissions/ Finalized processes/ Informational items only (no action required)
- [ ] Activity Grouping (Level 1) Each section contains grouped modules (collapsible): Examples: Model Year Reports/ Credit Applications/ Credit Transfers / ZEV Models/ Legacy Reassessment / Legacy Supplementary Reports

Activity Grouping (Level 1) Each group displays:
- [ ] Module name
- [ ] Count of items (e.g. “1 Draft”, “2 Submitted”)
- [ ] Expand/collapse control

Expanded View (Level 2) When a group is expanded: Each item must display:
- [ ] Last activity date (Based on most recent event)
- [ ] Item description (Clear and concise, e.g 1 saved as a draft/ Range information requested / Rejected by BC Gov)
- [ ] Primary action (CTA) Each item must include one primary action, aligned with its state. Examples: Continue Model Year Report (2024)/ Complete Range Information/ Review Rejected Model/ View Credit Transfer/ View Credit Agreement
- [ ] CTA must be action-oriented (verb-based) avoid system language (e.g. “Check”, “See details”)

Interaction Behavior
- [ ] Clicking the group expands/collapses items
- [ ] Clicking CTA navigates user to the relevant module/page
- [ ] The final design follow the design provided in Figma, including layout, spacing, typography, and component behavior.
- [ ] All dimensions, styles, and interaction patterns are defined in the Figma file followed

**Additional context**
Please provide feedback if more detailed definitions are required for specific activity types or CTA labels