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 notifications appear in the bell in the top bar and in a full notification center, each with its business, a link to the record and an unread marker you can clear with Mark All Read. Choose which events reach the bell, and have overdue invoices and expired estimates emailed to you as well.
- Event-specific context
- Unread markers and Mark All Read
- Bell for every event, email for two
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.
Unread markers and Mark All Read
The notification center shows how many items are new, marks each unread item with a dot, and lets you mark one item or use Mark All Read. The bell panel's footer links to All Notifications and to Notification Settings.
- All history
- Unread dot and new count
- 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
- Older notifications still open
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.
- Older notifications stay readable
- No guessed profile
- Safest list action
Choose each channel
Every event can be switched on or off for the bell; two can also be emailed to you.
Recommended defaults, then explicit choices
Events you haven't set yet use sensible defaults. Saving writes a clear On or Off choice for each event's bell, and for email on Invoice overdue and Estimate expired, the two events that offer it. Both emails start switched off.
- Email only where it is offered
- Whitelisted event keys
- No silent 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, recurring-created, payment-needs-review and scheduled-email-sent events.
-
Estimates
Sent, viewed, accepted, declined and expired events.
-
Proposals
Sent, viewed, accepted, declined and expiring events.
-
Projects
Assignments, time entries, budgets, long-running timers, submitted and approved timesheets, and hours a client approved or disputed.
-
Worklogs
Invoice or estimate creation from selected work.
-
Inventory
Reorder point reached arrives in the bell once you switch on the reorder alert in your inventory settings. Stock alerts are never emailed.
-
Recurring activity
Recurring income and expense events.
-
Team and portals
Team, customer-portal and vendor-portal join events, and a customer stopping or restarting a recurring schedule.
-
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?
In the bell at the top of every page. It shows recent activity, and its footer links to All Notifications, the full notification center where new items are marked, and to Notification Settings through the gear. Mark All Read clears the unread markers.
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?
For two events. Invoice overdue and Estimate expired can also be emailed to you, and both emails start switched off. Every other event arrives in the bell only, and Notification Settings, opened from the gear in the bell panel, lets you choose which ones.
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 switch on email for overdue invoices or expired estimates if you want them away from the workspace.
- No card required to start
- Configuration stays visible
- Current product boundaries stated