Admin Dashboard Notifications Selection
Summary
Section titled “Summary”The Admin Dashboard Notifications Selection mockup explores a dense notification widget where an agency admin can select specific unread notifications and mark them as read without affecting the whole list.
Mockup Snapshot
Section titled “Mockup Snapshot”| Field | Value |
|---|---|
| Company | JMS |
| Portal | Admin |
| Prototype | https://jms.orchidux.com/admin/notifications-selection |
| Jira tickets | Not linked yet |
| PRD | Not linked yet |
| Handoff status | In review |
| Walkthrough video | Not attached yet |
Approval State
Section titled “Approval State”Alfredo selected this variant over the Codex variant and approved checkbox-only row selection plus the title select-all checkbox. Product approval from Blakely is still open, so this page records the in-review handoff without promoting it as final product behavior.
Proposed Behavior
Section titled “Proposed Behavior”- The widget lists unread notifications only.
- Every row carries a persistent checkbox.
- The checkbox is the only selection target.
- A select-all checkbox sits beside the Notifications title.
- The existing header action changes from Mark all as read to Mark N as read when rows are selected.
- Marking rows as read removes them from the widget and shows inline confirmation.
- Empty state and loading/error behavior remain open until the data source is wired.
Open Questions
Section titled “Open Questions”- Should clicking a row open the notification?
- Should mark-read support undo?
- Does Mark all as read apply to every unread notification or only loaded rows?
- Is the unread count chip useful when the admin shell already carries a count?
- What loading and error states should production use?
Open Follow-Up
Section titled “Open Follow-Up”Keep this documentation tied to the mockup row, then update the UX Registry documentation URL after the row is created or finalized.