Rich event presentation
Each item uses an event-specific icon, tone and category plus the recorded business, document or workflow detail available at creation time.
- Category and title
- Business identity snapshot
- Relative time and unread state
Workflow awareness
Turn important business events into clear next actions
Invoice Crowd presents event-specific notifications in the header and a full notification center, with business context, safe application-relative actions, All and Unread views, and explicit Bell and Email preferences.
- Event-specific context
- All and Unread views
- Explicit Bell and Email choices
Last updated:
How it works
A notification should explain what changed and where to go
The current presenter carries category, title, supporting text, business identity, relative time, unread state and the safest available action across both the bell and notification center.
See the event
Recent history appears in the header; the full center keeps a paginated record.
All and Unread views
The notification center separates the complete history from items that still need attention and includes mark-one and mark-all-read actions.
- All history
- Unread filter
- Explicit read actions
Open the right record
Actions remain inside the application and are checked before navigation.
Event-specific destinations
Supported events can lead to the relevant invoice, estimate, proposal, project, worklog, expense, inventory, import, subscription or AI-credit surface.
- Record-aware action
- Application-relative paths only
- Legacy fallback actions
Historical honesty
Older rows are enriched from available facts. When an old event never recorded a unique document, amount or profile, the interface says so instead of guessing.
- Legacy rows remain readable
- No guessed profile
- Safest list action
Choose each channel
Bell and Email are independent, explicit preferences for known event keys.
Recommended defaults, then explicit choices
Missing legacy preferences use reviewed defaults. Saving writes a clear On or Off choice for each recognized Bell and Email event.
- Bell and Email separated
- Whitelisted event keys
- No silent scheduled-email opt-in
User scope and deliberate read state
Lists and read actions are scoped to the authenticated user. Brief hover, touch traversal and failed requests should preserve unread state; only the intentional read interaction commits it.
- Authenticated-user scope
- 650 ms continuous mouse hover
- Failed writes preserve unread
Capability map
Events, preferences and safety boundaries
The supported event families and the controls that prevent notification history from becoming an unscoped or misleading activity feed.
-
Invoices
Sent, first viewed, paid, overdue and recurring-created events.
-
Estimates
Sent, viewed, accepted and expired events.
-
Proposals
Sent, viewed, accepted and expiring events.
-
Projects
Assignments, time entries, budgets and long-running timer events.
-
Worklogs
Invoice or estimate creation from selected work.
-
Inventory
Low-stock and out-of-stock events.
-
Recurring activity
Recurring income and expense events.
-
Team and portals
Team, customer-portal and vendor-portal join events.
-
Imports
Import completion and failure events with relevant action context.
-
Subscriptions
Upcoming renewal awareness within the configured event policy.
-
AI credits
Low-credit events for the assistant workflow.
-
Retention
Read history is kept through the bounded notification retention path.
Questions
Notifications, answered
Where can I see my notifications?
The header bell shows recent activity and links to the full notification center, where you can switch between All and Unread views.
Can a notification open the affected record?
Yes, when authoritative action metadata exists. The action must be application-relative and is validated before the interface navigates to the relevant record or list.
Can I choose Bell and Email separately?
Yes. Notification settings present explicit On or Off switches for both channels across the recognized event catalog.
Are old notifications still understandable?
The presenter maps older rows to the safest known category, icon and destination. It states when historical details were not recorded instead of inventing a specific profile, amount or document.
Can one user mark another user's notification read?
No. Notification lists and read actions are scoped to the authenticated user; a public identifier from another account is not sufficient authority.
Does briefly passing the pointer over an item mark it read?
No. The deliberate hover interaction requires a continuous 650 milliseconds with a mouse. Brief hover, touch traversal and failed read requests preserve the unread state.
Keep the important events visible without turning on every channel
Start with Bell alerts, review the recommended defaults, and enable email only for events that genuinely need attention away from the workspace.
- No card required to start
- Configuration stays visible
- Current product boundaries stated