BC
Brad CodyAdministrator
Current product→Access and application shell
Reverse spec drafted

Notification centre

User-facing notification access from the authenticated header.

Observed route/adminFuture Spec 03 →
Current maturityVisible entry; panel and delivery state unverified
Evidence confidencePartially verified
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

Current-state summary

A Notifications control is present in the Overview header. The panel, unread indicator, grouping, mark-read behavior, record links and synchronization with the Notifications Builder have not been reviewed. This is distinct from the Settings Notifications Builder, which configures templates and delivery behavior.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

ElementCurrent behaviorVerification
Notification triggerA notification icon appears in the Overview top utility bar.Verified live
Unread count or indicatorNot observed in the current review.Unverified
Notification list or panelNot opened.Unverified

User journeys

Current flows

01

Open an alert

  1. Open Notifications
  2. Review unread and recent items
  3. Select one item
  4. Open the authorized linked record
  5. Update read state
Observed result

Only the entry point is verified.

State model

Current and expected states

No visible alert

Notification icon is present without a verified count.

Unread

Not verified.

Panel open

Not verified.

Loading or error

Not verified.

Cross-Workspace notification

Scoping behavior not verified.

Product rules

Non-negotiable boundaries

  • Notifications are scoped to the recipient and active Workspace.
  • A notification never grants access to its linked record.
  • Template editing cannot change protected recipients or security behavior.
  • In-app and external deliveries should reference the same domain event where applicable.
Dependencies
Notification definitionsNotification Builder templatesRecipient rulesDomain eventsRead stateRecord authorization

Known current limitations · 3 mapped

What is missing, broken or unverified

Future Spec 03 owns closure →
  1. Notification panel behavior is not documented.
  2. Unread counts, preferences, grouping, dismissal and mark-all-read are unknown.
  3. The relationship between current in-app alerts and Resend delivery is unverified.

Future alignment

Required evolution

  • 01Provide actionable grouping, record links, read state and clear Workspace context.
  • 02Add every new operational event to the editable template system within protected rules.
  • 03Expose delivery and failure state where appropriate.

Current baseline

Acceptance record

  • The notification entry point is present.
  • The profile distinguishes the user centre from the Settings builder.
  • Unverified delivery behavior remains explicit.

Reverse-spec completeness

Documentation coverage

The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.

Purpose and user outcome

Documented

Roles and access

Documented

Routes and entry points

Documented

Page and component anatomy

Documented

Fields and displayed data

Documented

Primary actions

Documented

Forms and validation

Documented

States and transitions

Documented

Empty, loading and error states

Documented

Responsive behavior

Partial

Accessibility behavior

Partial

Activity and audit events

Partial

Data sources and persistence

Documented

Notifications and automation

Partial

Known defects and limitations

Documented

Reusable component dependencies

Documented

Future-spec conflicts

Partial

Visual and repository evidence

Deferred

Acceptance of current baseline

Documented
← Feature inventoryOpen Future Spec 03 →